Re: Request: pg_cancel_backend variant that handles 'idle in transaction' sessions

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Request: pg_cancel_backend variant that handles 'idle in transaction' sessions
Date: 2015-11-04 21:15:28
Message-ID: CAFj8pRCAh2tfu7r9K1cx0PWcS2PJ5mdjnqfP7soBJ2kOpVFJrg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2015-11-04 22:14 GMT+01:00 Joshua D. Drake <jd(at)commandprompt(dot)com>:

> On 11/04/2015 01:11 PM, Pavel Stehule wrote:
>
>
>> I am sorry, but I have a different experience from GoodData. The few
>> hours autovacuum is usual. So probably, there should be exception for
>> autovacuum, dump, ..
>>
>
> But autovacuum and dump are not idle in transaction or am I missing
> something?
>

last Merlin's proposal was about transaction_timeout not
transaction_idle_timeout

Regards

Pavel

>
> JD
>
>
> --
> Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
> PostgreSQL Centered full stack support, consulting and development.
> New rule for social situations: "If you think to yourself not even
> JD would say this..." Stop and shut your mouth. It's going to be bad.
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2015-11-04 21:17:31 Re: Request: pg_cancel_backend variant that handles 'idle in transaction' sessions
Previous Message Joshua D. Drake 2015-11-04 21:14:17 Re: Request: pg_cancel_backend variant that handles 'idle in transaction' sessions