| From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
|---|---|
| To: | Chris Angelico <rosuav(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: database corruption questions |
| Date: | 2012-10-14 04:29:31 |
| Message-ID: | 507A3FAB.1080402@ringerc.id.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/14/2012 12:02 PM, Chris Angelico wrote:
>
> Is there an article somewhere about how best to do a plug-pull test?
> Or is it as simple as "fire up pgbench, kill the power, bring things
> back up, and see if anything isn't working"?
That's what I'd do and what I've always done in the past, but others
here are much more experienced with testing gear into production.
You can also use pg_test_fsync and diskchecker.pl . See:
http://www.postgresql.org/docs/current/static/wal-reliability.html
I do repeated plug-pull tests and make sure fsync is being honoured.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jasen Betts | 2012-10-14 04:54:34 | Re: Suggestions for the best strategy to emulate returning multiple sets of results |
| Previous Message | Chris Angelico | 2012-10-14 04:02:06 | Re: database corruption questions |