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> |
Subject: | Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade |
Date: | 2022-02-17 16:35:00 |
Message-ID: | 4eac5413-4267-d8e2-4d94-205d5256c498@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2/17/22 01:16, Tomas Vondra wrote:
> ...
>
>> How large is the table/index? Are you able to run the query with a
>> custom build (without values optimized out)? Any chance you still
>> have a
>> backup from before the pg_upgrade, on which you might run the query?
>>
>>
>> Yes, this is a test DB restored from backup in order to test out 14
>> upgrade, production is still running on 12.9.
>> v3_region is 2832 kB
>> region_ltree_path_idx_gist is 472 kB
>>
>
> That means it should be possible to reproduce the issue elsewhere by
> copying the files (and schema). Is there any sensitive data that'd
> prevent handing over this data?
>
Maybe we could also try just dumping the data (the ltree_path column),
so that we can load it into 12 cluster and do a binary upgrade. That
would be simpler than trying to copy the existing data files.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Japin Li | 2022-02-17 16:38:21 | Re: BUG #17409: Unable to alter data type of clustered column which is referenced by foreign key |
Previous Message | Tomas Vondra | 2022-02-17 16:29:37 | Re: BUG #17406: Segmentation fault on GiST index after 14.2 upgrade |