| From: | Daryl Stultz <daryl(dot)stultz(at)opentempo(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Corrupt index |
| Date: | 2017-08-15 19:51:03 |
| Message-ID: | CY4PR1601MB11259FFF0AD0EA2DB13DAC829E8D0@CY4PR1601MB1125.namprd16.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Aug 15, 2017 at 12:24 PM, Daryl Stultz
>>You've given no details at all. What business pattern? What does the
>>index and table look like?
Hi Peter. There are no details that are obvious to me that I should be providing. The business process is one of a thousand that the application performs. To describe it generically, if we were running a commerce website, every time we find ourselves in this situation the record is related to a cancelled order. Something like that.
The primary key of the table is of "serial" type with an index like so:
"scheduledassignments_pk" PRIMARY KEY, btree (scheduledassignmentid)
We have various triggers on the table.
Since the DB is managed by Amazon, I'm inclined to think the system is set up properly and the hardware is solid. This leaves me to consider some pattern in SQL, transactions and such that we are running that might be causing the corruption. Basically I don't have any idea what to look for.
/Daryl
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daryl Stultz | 2017-08-15 19:54:56 | Re: Corrupt index |
| Previous Message | Andreas Kretschmer | 2017-08-15 19:48:51 | Re: Corrupt index |