From: Tom Lane <tgl@sss.pgh.pa.us>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: Goulet, Dick <DGoulet@vicr.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: hanging for 30sec when checkpointing
Date: Tue, 10 Feb 2004 11:41:33 -0500
Message-ID: <15924.1076431293@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.33.0402100910400.28531-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0402100910400.28531-100000@css120.ihs.com>
"scott.marlowe" <scott.marlowe@ihs.com> writes:
>> Unfortunately not --- at checkpoint time, the constraint goes the other
>> way. We have to be sure all the data file updates are down to disk
>> before we write a checkpoint record to the WAL log. So you can still
>> get screwed if the data-file drive lies about write completion.
> Hmmm. OK. Would the transaction size be an issue here? I.e. would small
> transactions likely be safer against corruption than large transactions?
Transaction size would make no difference AFAICS. Reducing the interval
between checkpoints might make things safer in such a case.
> I ask because most of the testing I did was with pgbench running 100+
> simos (on a -s 100 pgbench database) and as long as the WAL drive was
> fsyncing correctly, the database survived.
Did you try pulling the plug immediately after a CHECKPOINT command
completes? You could test by manually issuing a CHECKPOINT while
pgbench runs, and yanking power as soon as the prompt comes back.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, scott.marlowe@ihs.com, DGoulet@vicr.com
Subject: Re: hanging for 30sec when checkpointing
In-Reply-To: <15924.1076431293@sss.pgh.pa.us>
References: <Pine.LNX.4.33.0402100910400.28531-100000@css120.ihs.com> <15924.1076431293@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox