On Mon, Dec 14, 2015 at 6:47 AM, Aleksander Alekseev
<a.aleks...@postgrespro.ru> wrote:
> Here is my fix for item 4.

I don't know, I'm still not very comfortable with this.  And Tom
didn't like dictating that hash_any() must be no-fail, though I'm not
sure why.

Let's wait to see what others think.  I kind of hope there's a way of
getting the benefits we want here without so much code churn.

Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to