Re: BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases - Mailing list pgsql-bugs

From John R Pierce
Subject Re: BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases
Date
Msg-id 4F7B2A5E.8060004@hogranch.com
Whole thread Raw
In response to Re: BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases  (Alex Matzinger <amatzinger@experts-exchange.com>)
List pgsql-bugs
On 04/03/12 9:40 AM, Tom Lane wrote:
> Alex Matzinger<amatzinger@experts-exchange.com>  writes:
>> >  The connection that is executing the SELECT 1 are generally open for 1-5
>> >  hours before they are killed.  The specific connection only executes
>> >  SELECT 1.  The transaction is simply BEGIN, and then SELECT 1's, no
>> >  other query is executed.
> Lose the "BEGIN" and it will probably work more nicely.


indeed,a  1-5 hour long transaction means VACUUM can't clean up anything
newer than the oldest active transaction, and thats not per database,
thats cluster-wide.



--
john r pierce                            N 37, W 122
santa cruz ca                         mid-left coast

pgsql-bugs by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases
Next
From: umi.tanuki@gmail.com
Date:
Subject: BUG #6572: The example of SPI_execute is bogus