Re: Collation-aware comparisons in GIN opclasses

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: Collation-aware comparisons in GIN opclasses
Дата
Msg-id CAM3SWZR2QsemVHg+81K_uWs9JXyyYQG9XuZnZFxjO0vma3h9Og@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Collation-aware comparisons in GIN opclasses  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Collation-aware comparisons in GIN opclasses  (Bruce Momjian <bruce@momjian.us>)
Список 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 по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: jsonb format is pessimal for toast compression
Следующее
От: Josh Berkus
Дата:
Сообщение: Re: jsonb format is pessimal for toast compression