| From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
|---|---|
| To: | Carlos Henrique Reimer <carlos(dot)reimer(at)opendb(dot)com(dot)br> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Exit code -1073741819 |
| Date: | 2013-08-07 22:48:11 |
| Message-ID: | CAL_0b1vT+x6ZHCHemPwADP4EuvQBkmMpF77LYQRUUugpfXTwgw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Aug 7, 2013 at 2:46 PM, Carlos Henrique Reimer
<carlos(dot)reimer(at)opendb(dot)com(dot)br> wrote:
> Could finally fix it. Used the binary search approach to identify the wrong
> tuples and removed them by ctid, 9 rows were removed and all of them
> belonged to the same block.
It is good. I still highly recommend to recreate the table, because
the corruption might implicitly affect page headers too.
> I believe it is not easy to identify the root cause for the corruption but
> does any one have some directions I could follow to identify the root cause
> in order to prevent it to happen again?
Check logs, both system and postgres, for suspicious activity, find
out if there were any power problems, server resets, etc.
Upgrade your cluster to the latest version first of all, install a
RAID controller with BBU, perform periodical SQL backups, and the PITR
backups to be able to restore on a particular moment of time.
--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA
Profile: http://www.linkedin.com/in/grayhemp
Phone: USA +1 (415) 867-9984, Russia +7 (901) 903-0499, +7 (988) 888-1979
Skype: gray-hemp
Jabber: gray(dot)ru(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | S H | 2013-08-07 23:54:04 | Commit problem in read-commited isolation level |
| Previous Message | Carlos Henrique Reimer | 2013-08-07 21:46:31 | Re: Exit code -1073741819 |