Re: RC2 and open issues

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: RC2 and open issues
Date: 2004-12-24 15:46:27
Message-ID: 200412241546.iBOFkR718197@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Greg Stark wrote:
>
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
> > Maybe we need a hybrid approach: clean a few percent of the LRU end of
> > the ARC list in order to keep backends from blocking on writes, plus run
> > a clock scan to keep checkpoints from having to do much.
>
> Well if you just keep note of when the last clock scan started then when you
> get to the end of the list you've _done_ a checkpoint.
>
> Put another way, we already have such a clock scan, it's called checkpoint.
> You could have checkpoint delay between each page write long enough to spread
> the checkpoint i/o out over a configurable amount of time -- say half the
> checkpoint interval -- and be done with that side of things.

But don't you have to keep the WAL files around longer then.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-12-24 16:16:35 Re: RC2 and open issues
Previous Message Tom Lane 2004-12-24 15:44:34 Re: Slow tab completion (7.4)

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2004-12-24 16:00:57 Re: Allow pooled connections to list all prepared queries
Previous Message Simon Riggs 2004-12-23 21:26:16 Re: Bgwriter behavior