Re: Collation-aware comparisons in GIN opclasses - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Collation-aware comparisons in GIN opclasses
Date
Msg-id CAPpHfdufa1mVi5eeQSyWoQR_VMd4X=aXLtOQrdXLQYmoE=tNug@mail.gmail.com
Whole thread Raw
In response to Re: Collation-aware comparisons in GIN opclasses  (Emre Hasegeli <emre@hasegeli.com>)
Responses Re: Collation-aware comparisons in GIN opclasses  (Emre Hasegeli <emre@hasegeli.com>)
List pgsql-hackers
On Tue, Sep 16, 2014 at 11:29 AM, Emre Hasegeli <emre@hasegeli.com> wrote:
Changing the default opclasses should work if we make
pg_dump --binary-upgrade dump the default opclasses with indexes
and exclusion constraints.  I think it makes sense to do so in
--binary-upgrade mode.  I can try to come with a patch for this.

Can you explain it a bit more detail? I didn't get it.

------
With best regards,
Alexander Korotkov.     

pgsql-hackers by date:

Previous
From: Emre Hasegeli
Date:
Subject: Re: Collation-aware comparisons in GIN opclasses
Next
From: Pavel Stehule
Date:
Subject: Re: Anonymous code block with parameters