Re: statement_timeout doesn't work - Mailing list pgsql-general

From Sergey Konoplev
Subject Re: statement_timeout doesn't work
Date
Msg-id CAL_0b1tvQUQ9DnXQr5Sx8-cPrYy-2HbNi=HvSP2e1705f0ngGw@mail.gmail.com
Whole thread Raw
In response to Re: statement_timeout doesn't work  (David G Johnston <david.g.johnston@gmail.com>)
Responses Re: statement_timeout doesn't work  (Sergey Konoplev <gray.ru@gmail.com>)
List pgsql-general
On Mon, Jul 21, 2014 at 10:16 AM, David G Johnston
<david.g.johnston@gmail.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.ru@gmail.com


pgsql-general by date:

Previous
From: David G Johnston
Date:
Subject: Re: Why would I need to explicitly cast a string literal to text?
Next
From: Kevin Grittner
Date:
Subject: Re: Why would I need to explicitly cast a string literal to text?