From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: richard.vesely@softea.sk
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18016: REINDEX TABLE failure
Date: Fri, 07 Jul 2023 20:20:01 -0400
Message-ID: <1457241.1688775601@sss.pgh.pa.us> (raw)
In-Reply-To: <ZKirERBzkM48E0op@paquier.xyz>
References: <18016-2bd9b549b1fe49b3@postgresql.org>
<ZKirERBzkM48E0op@paquier.xyz>
Michael Paquier <michael@paquier.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, richard.vesely@softea.sk, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18016: REINDEX TABLE failure
In-Reply-To: <1457241.1688775601@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox