From: | Greg Smith <greg(at)2ndQuadrant(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: archive_timeout behavior (8.4.6) |
Date: | 2011-05-02 04:09:36 |
Message-ID: | 4DBE2E80.50008@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 04/22/2011 08:23 PM, Brian Fehrle wrote:
> So long story short, if a cluster has zero activity, and
> archive_timeout is not set to 0, when it reaches that timeout should
> it generate a file, or just skip because it would be 100% empty?
You're right about what you've seen here, there is some logic in the
WAL/checkpoint code that can avoid doing anything when the timeout hits,
if there hasn't been any new WAL written since the last one. That
hasn't changed for a while now though (since I've been watching that
part of the source code at least) so I'm not sure what differences
between 8.4.6 and earlier 8.4 versions you think you've observed.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
"PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books
From | Date | Subject | |
---|---|---|---|
Next Message | Hiren Lad | 2011-05-02 07:48:37 | Postgresql 8.4 database server |
Previous Message | Greg Smith | 2011-05-02 04:01:59 | Re: Re: best practice for moving millions of rows to child table when setting up partitioning? |