| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jeffrey W(dot) Baker" <jwbaker(at)acm(dot)org> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_xlog becomes extremely large during CREATE INDEX |
| Date: | 2004-05-13 16:28:39 |
| Message-ID: | 9899.1084465719@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Jeffrey W. Baker" <jwbaker(at)acm(dot)org> writes:
> Sorry, my last mail got cut off. The server aborted because it couldn't
> write the xlog. Looks like I omitted this from my last mail:
Selective quoting of the log output? Naughty naughty.
However, that still doesn't explain how you got into the current state.
Had you once had checkpoint_segments set much higher than the current
value of 24? On looking at the code I see that it doesn't make any
attempt to prune future log segments after a decrease in
checkpoint_segments, so if a previous misconfiguration had allowed the
number of future segments to get really large, that could be the root of
the issue.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeffrey W. Baker | 2004-05-13 16:41:44 | Re: pg_xlog becomes extremely large during CREATE INDEX |
| Previous Message | Jeffrey W. Baker | 2004-05-13 16:02:10 | Re: pg_xlog becomes extremely large during CREATE INDEX |