Re: No control over max.num. WAL files - Mailing list pgsql-general

From Simon Riggs
Subject Re: No control over max.num. WAL files
Date
Msg-id BANLkTiku8nUf_XfK7-yWvjFLEm2swedKHQ@mail.gmail.com
Whole thread Raw
In response to Re: No control over max.num. WAL files  (Andrew Sullivan <ajs@crankycanuck.ca>)
Responses Re: No control over max.num. WAL files  (Scott Marlowe <scott.marlowe@gmail.com>)
Re: No control over max.num. WAL files  (Andrew Sullivan <ajs@crankycanuck.ca>)
List pgsql-general
On Wed, May 25, 2011 at 1:08 PM, Andrew Sullivan <ajs@crankycanuck.ca> wrote:

> Note that "unneeded".  Obviously, you need more than that, probably
> because you're restoring the database in one transaction (so none of
> the files can be flushed).

That's the way SQLServer and Oracle work, but not PostgreSQL. We can
clear down WAL files even during a long running transaction.

For us, "unneeded" means prior to the second-to-last checkpoint record.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-general by date:

Previous
From: Rafael Martinez
Date:
Subject: Re: No control over max.num. WAL files
Next
From: Scott Marlowe
Date:
Subject: Re: No control over max.num. WAL files