Re: BUG #18016: REINDEX TABLE failure
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: richard.vesely@softea.sk, pgsql-bugs@lists.postgresql.org
Date: 2023-07-08T00:20:01Z
Lists: pgsql-bugs, pgsql-hackers
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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Reindex toast before its main relation in reindex_relation()
- f2bf8fb04886 17.0 landed
-
Fix comment in index.c
- bd5760df38c0 17.0 landed
-
Clean up a bug in sql/json items commit 66ea94e8e6
- 06a66d87dbc7 17.0 cited
-
Create a "relation mapping" infrastructure to support changing the relfilenodes
- b9b8831ad60f 9.0.0 cited