Re: statement_timeout doesn't work

From: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
To: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: statement_timeout doesn't work
Date: 2014-07-21 18:32:06
Message-ID: CAL_0b1tvQUQ9DnXQr5Sx8-cPrYy-2HbNi=HvSP2e1705f0ngGw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jul 21, 2014 at 10:16 AM, David G Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>> So, If I separate the commands everything will will work as expected,
>> correct?
>
> I would assume so.
>
> If you wait to send the DROP/ALTER index commands until the SET LOCAL
> command returns successfully then both of those commands will die if they
> exceed the timeout specified.

Thank you. I'll try it.

--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA

http://www.linkedin.com/in/grayhemp
+1 (415) 867-9984, +7 (499) 346-7196, +7 (988) 888-1979
gray(dot)ru(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2014-07-21 18:34:07 Re: Why would I need to explicitly cast a string literal to text?
Previous Message David G Johnston 2014-07-21 17:56:22 Re: Why would I need to explicitly cast a string literal to text?