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

From Peter Geoghegan
Subject Re: Collation-aware comparisons in GIN opclasses
Date
Msg-id CAM3SWZR2QsemVHg+81K_uWs9JXyyYQG9XuZnZFxjO0vma3h9Og@mail.gmail.com
Whole thread Raw
In response to Re: Collation-aware comparisons in GIN opclasses  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Collation-aware comparisons in GIN opclasses
List pgsql-hackers
On Mon, Sep 15, 2014 at 12:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> No.  And we don't know how to change the default opclass without
> breaking things, either.

Is there a page on the Wiki along the lines of "things that we would
like to change if ever there is a substantial change in on-disk format
that will break pg_upgrade"? ISTM that we should be intelligently
saving those some place, just as Redhat presumably save up
ABI-breakage over many years for the next major release of RHEL.
Alexander's complaint is a good example of such a change, IMV. Isn't
it more or less expected that the day will come when we'll make a
clean break?


-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: jsonb format is pessimal for toast compression
Next
From: Josh Berkus
Date:
Subject: Re: jsonb format is pessimal for toast compression