| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CUBE seems a bit confused about ORDER BY |
| Date: | 2017-12-14 10:36:47 |
| Message-ID: | 3834058e-0ab9-be77-dccb-c57924adde0b@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> Yes. I bet only few users have built indexes over ~> operator if any.
>> Ask them to reindex in the release notes seems OK for me.
>>
>
> Is there a good way to detect such cases? Either in pg_upgrade, so that
> we can print warnings, or at least manually (which would be suitable for
> release notes).
Hmm, suppose, fix should be backpatched (because now it's unusable) and
pg_upgrade should not do anything. Just add release note to 10.0 and 11.0
Oh, check expression is affected too, users will need to reinsert data.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-12-14 10:45:48 | Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager |
| Previous Message | Ashutosh Bapat | 2017-12-14 10:31:01 | Re: [HACKERS] Partition-wise aggregation/grouping |