Re: No control over max.num. WAL files

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: No control over max.num. WAL files
Date: 2011-05-25 12:37:47
Message-ID: BANLkTiku8nUf_XfK7-yWvjFLEm2swedKHQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, May 25, 2011 at 1:08 PM, Andrew Sullivan <ajs(at)crankycanuck(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2011-05-25 12:44:34 Re: No control over max.num. WAL files
Previous Message Rafael Martinez 2011-05-25 12:32:52 Re: No control over max.num. WAL files