Skip site navigation (1) Skip section navigation (2)

Re: URGENT: Out of disk space pg_xlog

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: ohp(at)pyrenet(dot)fr
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Jeremy Haile <jhaile(at)fastmail(dot)fm>, pgsql-performance(at)postgresql(dot)org
Subject: Re: URGENT: Out of disk space pg_xlog
Date: 2006-12-22 20:25:43
Message-ID: 20061222202543.GA12031@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-performance
ohp(at)pyrenet(dot)fr wrote:
> On Fri, 22 Dec 2006, Tom Lane wrote:
> 
> > Date: Fri, 22 Dec 2006 13:14:18 -0500
> > From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> > To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
> > Cc: Jeremy Haile <jhaile(at)fastmail(dot)fm>, pgsql-performance(at)postgresql(dot)org
> > Subject: Re: [PERFORM] URGENT: Out of disk space pg_xlog
> >
> > "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> > > As I understand it, the log space accumulates for the oldest transaction
> > > which is still running, and all transactions which started after it.
> >
> > No, pg_xlog can be truncated as soon as a checkpoint occurs.
> 
> Even for currently running transactions ?
> 
> My understanding was that checkpoint was syncing data files for commited
> transactions.

No, it syncs data files for all transactions, even those currently
running.

> What happens to pg_xlogs when a transaction updates M of rows/tables and
> runs for hours?

They get recycled as the update goes.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

pgsql-performance by date

Next:From: Steinar H. GundersonDate: 2006-12-22 20:29:36
Subject: Re: URGENT: Out of disk space pg_xlog
Previous:From: Tom LaneDate: 2006-12-22 20:13:33
Subject: Re: URGENT: Out of disk space pg_xlog

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group