| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | cedric(at)dreamgnu(dot)com, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: archive wal's failure and load increase. |
| Date: | 2006-09-29 14:53:40 |
| Message-ID: | 1159541620.2649.10.camel@holly |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, 2006-09-29 at 10:29 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > We discussed putting PreallocXlogFiles() in bgwriter once before, but I
> > think last time we discussed that idea it was rejected, IIRC.
>
> We already do that: it's called a checkpoint.
Yes, but not enough.
PreallocXlogFiles() adds only a *single* xlog file, sometimes.
On a busy system, that would be used up too quickly to make a
difference. After that the effect of adding new files would continue as
suggested.
If it did add more than one... it might work better for this case.
> It's a good thought but I don't think the theory holds water for
> explaining Cedric's problem, unless there was *also* some effect
> preventing checkpoints from completing ... which would be a much more
> serious problem than the archiver failing.
Still the best explanation for me.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-09-29 15:35:57 | Re: any hope for my big query? |
| Previous Message | Merlin Moncure | 2006-09-29 14:39:20 | Re: Performace Optimization for Dummies |