Re: what could cause inserts getting queued up and db locking??

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Brian Maguire" <bmaguire(at)vantage(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: what could cause inserts getting queued up and db locking??
Date: 2004-10-28 15:47:51
Message-ID: 2442.1098978471@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Brian Maguire" <bmaguire(at)vantage(dot)com> writes:
> What are the implications to further increasing the checkpoint so say
> 40?

AFAIK the downsides are (a) more disk space eaten for pg_xlog,
(b) if you suffer a crash, it will take longer to recover (because
there'll be more uncheckpointed work to replay); (c) the checkpoint
itself could require more I/O because there's more pending write
activity.

> Also how does 8.0's background-writer feature work and what are going to
> benefits?

The idea of the bgwriter is to trickle out disk writes continuously
instead of having a big write storm at each checkpoint.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tim Vadnais 2004-10-28 16:14:17 field incrementing in a PL/pgSQL trigger
Previous Message Brian Maguire 2004-10-28 15:24:53 Re: what could cause inserts getting queued up and db locking??