| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Subject: | Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade |
| Date: | 2022-02-24 21:17:27 |
| Message-ID: | 6bc7e8a7-382f-9d8d-8b8d-9c6607f7fa15@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2/24/22 19:36, Tomas Vondra wrote:
>
> ...
>
> Attached is a patch that fixes this, but I wonder what will happen to
> new indexes created on 13+. Will check.
>
Unfortunately, the patch fixes indexes built on PG12, but it also breaks
indexes created after pg_upgrade :-(
I'm not sure if a good solution even exists, because we can't really
distinguish those indexes. It only affects ltree_gist, though, and we
didn't get any other reports so far, so either few people are using it
or have not upgraded yet.
I've created a thread on pgsql-hackers [1], where it might get more
attention from other developers. Maybe they'll have a better idea on how
to fix this.
regards
[1]
https://www.postgresql.org/message-id/d80e0a55-6c3e-5b26-53e3-3c4f973f737c%40enterprisedb.com
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-02-25 01:51:28 | Re: Wal sender process not moving past wait_event_type: IO and wait_event: WALRead |
| Previous Message | Tomas Vondra | 2022-02-24 18:36:40 | Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade |