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

From Alex Matzinger
Subject Re: BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases
Date
Msg-id 4F7DCA6C.5080806@experts-exchange.com
Whole thread Raw
In response to Re: BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases  (John R Pierce <pierce@hogranch.com>)
List pgsql-bugs
Dropping the BEGIN has cleared up the issue.  Thank you.

On 4/3/2012 9:50 AM, John R Pierce wrote:
> 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.
>
>
>

pgsql-bugs by date:

Previous
From: Lucian Curelaru
Date:
Subject: pg_ctl wrong status info on Windows
Next
From: Terrance Chen
Date:
Subject: Could not find your PostgreSQL installation in /var/lib/pgsql