From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Chris Angelico <rosuav(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Plug-pull testing worked, diskchecker.pl failed |
Date: | 2012-10-22 19:26:33 |
Message-ID: | CAMkU=1wNX=64jTbvdkR23gUkE9hWTR4nF_-tiDSr70HXQ8zt4w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Oct 22, 2012 at 6:17 AM, Chris Angelico <rosuav(at)gmail(dot)com> wrote:
> After reading the comments last week about SSDs, I did some testing of
> the ones we have at work - each of my test-boxes (three with SSDs, one
> with HDD) subjected to multiple stand-alone plug-pull tests, using
> pgbench to provide load. So far, there've been no instances of
> PostgreSQL data corruption, but diskchecker.pl reported huge numbers
> of errors.
What did you do to look for corruption? That PosgreSQL succeeds at
going through crash-recovery and then starting up is not a good
indicator that there is no corruption.
Did you do something like compute the aggregates on pgbench_history
and compare those aggregates to the balances in the other 3 tables?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Angelico | 2012-10-22 19:31:29 | Re: Plug-pull testing worked, diskchecker.pl failed |
Previous Message | Merlin Moncure | 2012-10-22 16:45:13 | Re: Revert TRUNCATE CASCADE? |