Corrupt index

From: Daryl Stultz <daryl(dot)stultz(at)opentempo(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Corrupt index
Date: 2017-08-15 19:24:29
Message-ID: CY4PR1601MB11254E29A4CECE38A258B8F89E8D0@CY4PR1601MB1125.namprd16.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello,

We are using PostgreSQL 9.3.14 on a managed Amazon RDS with a Multi-zone failover configuration. We do not have access to the hardware or file system. Fsync is enabled.

We have a recurring problem that we can get out of with "reindex table mytable". Basically we can't find a particular record or two using the primary key and after reindexing we can. There does seem to be a pattern related to application business processes but we are at a loss as to how this could happen.

Assuming the RDS instance is solid, what are the things we could do using nothing but SQL that could cause a corruption to the primary key index? I've researched the issue a fair amount and most content talks about hardware, file system, and fsync. As mentioned above fsync (and other properties) we can control (and fsync is enabled) but we can't get to the file system or hardware. If such a thing cannot be done with transactions, statements, and queries alone, what should we be looking at for settings?

Thanks.

--

Daryl Stultz
Principal Software Developer
_____________________________________
OpenTempo, Inc
http://www.opentempo.com<http://www.opentempo.com/>
mailto:daryl(dot)stultz(at)opentempo(dot)com<mailto:daryl(dot)stultz(at)opentempo(dot)com>

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Geoghegan 2017-08-15 19:29:40 Re: Corrupt index
Previous Message Andreas Kretschmer 2017-08-15 06:35:38 Re: cluster question