Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Sat, 27 Oct 2007 10:04:20 -0400
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
- References:
- WAL archiving idle database
- From: Brian Wipf
- Re: WAL archiving idle database
- From: Jeff Davis
- Re: WAL archiving idle database
- From: Simon Riggs
- WAL archiving idle database
- Prev by Date: Re: Postgres+Apache+PHP (again, but in different setup)
- Next by Date: Re: I want to search my project source code
- Previous by thread: Re: WAL archiving idle database
- Next by thread: find out data types using sql or php
- Indexes: