Re: pg_xlog becomes extremely large during CREATE INDEX - Mailing list pgsql-general

From Jeffrey W. Baker
Subject Re: pg_xlog becomes extremely large during CREATE INDEX
Date
Msg-id 1084464129.18156.0.camel@noodles
Whole thread Raw
In response to Re: pg_xlog becomes extremely large during CREATE INDEX  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Thu, 2004-05-13 at 06:10, Tom Lane wrote:
> "Jeffrey W. Baker" <jwbaker@acm.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

pgsql-general by date:

Previous
From: James M Moe
Date:
Subject: Re: referential integrity constraints not checked inside
Next
From: Tom Lane
Date:
Subject: Re: pg_xlog becomes extremely large during CREATE INDEX