Re: Hash support for row types - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Hash support for row types
Date
Msg-id CA+TgmobT6e4uV6JNMND7oM23Q8HUAgyEP4R1w9-G9w9jT0stDg@mail.gmail.com
Whole thread Raw
In response to Re: Hash support for row types  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Hash support for row types  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Oct 20, 2020 at 11:10 AM Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 2020-10-20 01:32, Andres Freund wrote:
> > How does this deal with row types with a field that doesn't have a hash
> > function? Erroring out at runtime could cause queries that used to
> > succeed, e.g. because all fields have btree ops, to fail, if we just have
> > a generic unconditionally present hash opclass?  Is that an OK
> > "regression"?
>
> Good point.  There is actually code in the type cache that is supposed
> to handle that, so I'll need to adjust that.

Do we need to worry about what happens if somebody modifies the
opclass/opfamily definitions?

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [PATCH] SET search_path += octopus
Next
From: Alvaro Herrera
Date:
Subject: Re: CREATE TABLE .. PARTITION OF fails to preserve tgenabled for inherited row triggers