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

From: John R Pierce <pierce(at)hogranch(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-03 16:50:38
Message-ID: 4F7B2A5E.8060004@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message umi.tanuki 2012-04-04 01:42:01 BUG #6572: The example of SPI_execute is bogus
Previous Message Kevin Grittner 2012-04-03 16:41:38 Re: BUG #6571: Postgres Kills 'Select 1' query randomly on hot standby databases