From: Jeremy Haile <jhaile@fastmail.fm>
To: pgsql-performance@postgresql.org
Subject: Re: URGENT: Out of disk space pg_xlog
Date: Fri, 22 Dec 2006 12:39:48 -0500
Message-ID: <1166809188.18931.281714145@webmail.messagingengine.com> (raw)
In-Reply-To: <1166809000.3783.206.camel@silverbirch.site>
References: <1166803606.2828.281701761@webmail.messagingengine.com>
<1166806378.10592.281708161@webmail.messagingengine.com>
<1166806963.3783.203.camel@silverbirch.site>
<1166808625.17094.281711491@webmail.messagingengine.com>
<1166809000.3783.206.camel@silverbirch.site>
checkpoint_segments has been set at 12 for a while and was never set
higher than that. (before that it was set to the PG default - 3 I think)
Before the server crashed I was running an update that updates a boolean
flag on two large tables (10 million rows each) for transactions older
than today (roughly 80% of the rows) The transaction ran for a long
time and I assume is what caused the pg_xlog to fill up.
On Fri, 22 Dec 2006 17:36:39 +0000, "Simon Riggs"
<simon@2ndquadrant.com> said:
> On Fri, 2006-12-22 at 12:30 -0500, Jeremy Haile wrote:
> > The archive_status directory is empty. I've never seen any files in
> > there and I've never set archive_command.
> >
> > Well, the problem has since resolved, but here is what is in the
> > directory now. Previously there were hundreds of files, but these
> > disappeared after Postgres performed the automatic recovery.
>
> What were you doing before the server crashed?
>
> Did you previously have checkpoint_segments set higher? When/how was it
> reduced?
>
> --
> Simon Riggs
> EnterpriseDB http://www.enterprisedb.com
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: jhaile@fastmail.fm
Subject: Re: URGENT: Out of disk space pg_xlog
In-Reply-To: <1166809188.18931.281714145@webmail.messagingengine.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox