Re: Collation-aware comparisons in GIN opclasses

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Emre Hasegeli <emre(at)hasegeli(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Geoghegan <pg(at)heroku(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Collation-aware comparisons in GIN opclasses
Date: 2014-09-16 07:42:03
Message-ID: CAPpHfdufa1mVi5eeQSyWoQR_VMd4X=aXLtOQrdXLQYmoE=tNug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 16, 2014 at 11:29 AM, Emre Hasegeli <emre(at)hasegeli(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2014-09-16 07:44:17 Re: Anonymous code block with parameters
Previous Message Emre Hasegeli 2014-09-16 07:29:52 Re: Collation-aware comparisons in GIN opclasses