Re: Index corruption revealed after upgrade to 11.17, could date back to at least 11.12 - Mailing list pgsql-general

From Peter J. Holzer
Subject Re: Index corruption revealed after upgrade to 11.17, could date back to at least 11.12
Date
Msg-id 20221028202447.aoagwsal5j5ti5by@hjp.at
Whole thread Raw
In response to Re: Index corruption revealed after upgrade to 11.17, could date back to at least 11.12  (Kristjan Mustkivi <sonicmonkey@gmail.com>)
Responses Re: Index corruption revealed after upgrade to 11.17, could date back to at least 11.12
List pgsql-general
On 2022-10-28 17:23:02 +0300, Kristjan Mustkivi wrote:
> By the way, index rebuild while completing successfully did not fix
> the indexes - the data in the tables was still missing even after the
> successful rebuild command.

This is surprising. As I understand it, REINDEX scans the complete table
and builds a new index. So after a REINDEX the index should be complete
and usable.

However, reading
https://www.postgresql.org/docs/current/sql-reindex.html I'm unsure what
happens if you have issued a REINDEX for a table, schema, etc. and
rebuilding an index fails: Does it abort at that time or does it just
issue a notice and continue to rebuild the other indexes? In the latter
case it migh be easy to miss a problem.

        hp


--
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"

Attachment

pgsql-general by date:

Previous
From: Vijaykumar Sampat Jain
Date:
Subject: Re: ERROR: could not find pathkey item to sort
Next
From: Bryn Llewellyn
Date:
Subject: "peer" authentication: cannot make "pg_ident.conf" work as I believe that the doc says that it should