| From: | "Jeffrey W(dot) Baker" <jwbaker(at)acm(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:02:10 |
| Message-ID: | 1084464129.18156.0.camel@noodles |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 2004-05-13 at 06:10, Tom Lane wrote:
> "Jeffrey W. Baker" <jwbaker(at)acm(dot)org> writes:
> > Oh sure, it's bleating. Apparently my computer is too fast:
>
> I don't think the checkpoint process is completing.
>
> > May 12 16:37:08 mistral postgres[506]: [174-1] LOG: server process (PID 16403) was terminated by signal 6
>
> You need to find out why these aborts (presumably Assert failures) are
> occurring. Having just looked at the source code, I see that Assert
> messages are never sent to syslog only to stderr. So you'll want to
> set things up to capture the postmaster's stderr instead of discarding it.
The server process aborted when the device filled up.
-jwb
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-05-13 16:28:39 | Re: pg_xlog becomes extremely large during CREATE INDEX |
| Previous Message | James M Moe | 2004-05-13 15:26:37 | Re: referential integrity constraints not checked inside |