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

From Tom Lane
Subject Re: pg_xlog becomes extremely large during CREATE INDEX
Date
Msg-id 7619.1084453823@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_xlog becomes extremely large during CREATE INDEX  ("Jeffrey W. Baker" <jwbaker@acm.org>)
Responses Re: pg_xlog becomes extremely large during CREATE INDEX  ("Jeffrey W. Baker" <jwbaker@acm.org>)
List pgsql-general
"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.

            regards, tom lane

pgsql-general by date:

Previous
From: Christian Rank
Date:
Subject: Re: referential integrity constraints not checked inside
Next
From: Christopher Browne
Date:
Subject: Re: referential integrity constraints not checked inside PL/pgSQL functions?