Re: WAL archiving idle database

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Brian Wipf <brian(at)clickspace(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: WAL archiving idle database
Date: 2007-10-27 14:04:20
Message-ID: 16326.1193493860@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> We *could* force it to perform a log switch whether or not new WAL has
> been written.

That would be a truly awful idea.

I think the right answer for Kevin's situation really is to be doing a
dummy transaction every few minutes as one component of his system
monitoring. That way he gets the behavior he wants, and it needn't
preclude us from fixing the default behavior to be less wasteful.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-10-27 14:25:05 Re: I want to search my project source code
Previous Message Matthew Wilson 2007-10-27 13:01:31 I want to search my project source code

Browse pgsql-hackers by date

  From Date Subject
Next Message Camilo Porto 2007-10-27 14:10:06 Re: URGENT HELP about 'duration' stats
Previous Message Pavel Stehule 2007-10-27 14:01:15 Re: Proposal: real procedures again (8.4)