Skip site navigation (1) Skip section navigation (2)

Re: BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases

From: Alex Matzinger <amatzinger(at)experts-exchange(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases
Date: 2012-04-05 16:38:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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(at)experts-exchange(dot)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.

In response to

pgsql-bugs by date

Next:From: iiheroDate: 2012-04-05 23:19:34
Subject: Re: Could not find your PostgreSQL installation in /var/lib/pgsql
Previous:From: Lucian CurelaruDate: 2012-04-05 15:22:28
Subject: pg_ctl wrong status info on Windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group