| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WAL/PITR additional items |
| Date: | 2005-04-20 23:41:28 |
| Message-ID: | 2216.1114040488@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> writes:
> On Wed, 20 Apr 2005, Tom Lane wrote:
>> What?
> The discussion Simon is refering to came up during the 8.0 beta IIRC. The
> problem was that we were not allocating xlogs quickly enough under
> heavy workloads and there was some discussion about the bgwriter taking
> over this task since it could assess the need for new xlogs more often.
Huh? The bgwriter already has this task, since it runs checkpoints.
It's possible that we ought to allow more "slop" in the number of
prealloc'd xlog segments --- I think that the current code is probably
too enthusiastic about deleting "extra" segments after a spike in
activity subsides. But I don't see the point of moving the
responsibility somewhere else.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2005-04-20 23:54:47 | Re: WAL/PITR additional items |
| Previous Message | Gavin Sherry | 2005-04-20 23:34:41 | Re: WAL/PITR additional items |