From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | richard(dot)vesely(at)softea(dot)sk, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18016: REINDEX TABLE failure |
Date: | 2023-07-08 00:20:01 |
Message-ID: | 1457241.1688775601@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Thu, Jul 06, 2023 at 08:29:19PM +0000, PG Bug reporting form wrote:
>> Given a table with a TOASTed variable length attribute, REINDEX TABLE fails
>> to rebuild indexes when you truncate (or otherwise corrupt) relation files
>> for both TOAST table index and a custom index on the varlena.
> Could you clarify what you have done here? Did you manipulate the
> physical files in the data folder before running the REINDEX commands
> you expected should work? There are many things that can go wrong if
> you do anything like that.
I think the point of that was just to have a way to reproduce the problem
on-demand. I follow the argument, which is that if there's actual
corruption in the TOAST index (for whatever reason) that might interfere
with rebuilding the table's other indexes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2023-07-08 12:48:00 | Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() |
Previous Message | Michael Paquier | 2023-07-08 00:17:21 | Re: BUG #18016: REINDEX TABLE failure |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2023-07-08 01:00:51 | Re: [PoC] Federated Authn/z with OAUTHBEARER |
Previous Message | Michael Paquier | 2023-07-08 00:17:21 | Re: BUG #18016: REINDEX TABLE failure |