tree 499c475ffab847377951ad5a2f5d9cd40eba9855
parent 8ddb3f82e997d1a10619fc37ff7900823c7c0b91
author Stamatis Zampetakis <zabetak@gmail.com> 1632219770 +0200
committer Stamatis Zampetakis <zabetak@gmail.com> 1632219770 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQIzBAABCgAdFiEEBHSVd/2TRnS5zUXF13wzg/GSdXAFAmFJsnoACgkQ13wzg/GS
 dXBKcw/9F4hb4ULnmRWJTIDET4ciQZi+oyGshA9lhZy33ES3W2BaiV8J+oUKY37i
 TXqLa4pvUfxJlPVhWNGDswVt1IVh/rln0psewz+TLEsfRfT1cdfd64DevYxtaODU
 V0LSEbdljGOor6twYGKMzJ1e+L2D4Ldob8/4IkkQBy2J3Oy9ZQhhr8tWROHIOFn6
 djVoymNt+8XXcpPXZQ/uf64+zQb/NVPeU2PK0z9OqtWkThQka/nUyD8kZWfLwXXx
 fT0g8b8L6lLZEa3UZllSsNXqOC4seRxskAuuZvpaXreBF3DaE8bWJvyje/VCw3oh
 KJ0VtcW4cIaXKbuckWInyMycfBNiUj+8YS9TtEAyYcmwY4sH0ZBz2vzFScSNhUu0
 782EiDl6MfFmClstXKvFESU8PaX+7iZPfKH/dl+hwV2E5+1JjfSswC4gJBX4oUfW
 PL1nGqRo5Sv3saL1bzr7krmNE4WmhZUUJxmt9l0kXS5nYEH3j+PWhV10c+UBz1xn
 9jz9UpDDmHnsbXqOwFCo9ZOaj4I/URKYRe3HEYayIMP8Tfma10csGnfl6z1I6QwZ
 6borzEMKPJSCXAtXpdlXeXCHWbiSok6XslEnwswvZexGawSvL7SQok+RipZSrgFv
 Edtq6gFGiU9UZBwKGxAA3rI2SXzV2NEIuYY0xDQSNehR5Y8gqPw=
 =D4GT
 -----END PGP SIGNATURE-----

Remove obsolete/misleading comments in RelOptUtil#classifyFilters

The claim that filters are not pushed in the NULL generating side is not
true (at least not anymore).

Consider the following query:

SELECT *
FROM emp e
LEFT JOIN dept d
  ON d.deptno > 20

In this case the filter in the ON clause can be pushed in the right
which is the NULL generating side. This is already done by the
FilterJoinRule generating a plan similar to the query below.

SELECT *
FROM emp e
LEFT JOIN (SELECT * FROM dept d WHERE d.deptno > 20) ON true