Github user karthijrk commented on the issue:
Quick comment : We were trying to see if we can port this fix to gpdb. In
general, by design Postgres / GPDB doesn't check for null in low-level API.
Instead, when the arguments get evaluated, it sets the `isNull` flag
appropriately. Shouldn't the fix be to see why that flag was not set to true
when the argument was evaluated ?
For.eg. if we do select texteq(null, 'dfd') it doesn't crash because first
argument's `isNull` set to true and hence it didn't execute `texteq`.
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket