Re: statement_timeout is not working as expected with postgres_fdw

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: statement_timeout is not working as expected with postgres_fdw
Date: 2017-05-07 04:42:30
Message-ID: CAA4eK1KAH17sdF+7w-goR0UuGAGzCm-aJ0W=YxwDLG8EJrDJEQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 6, 2017 at 10:41 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sat, May 6, 2017 at 12:55 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> Oh! Good catch. Given that the behavior in question is intentional
>> there and intended to provide backward compatibility, changing it in
>> back-branches doesn't seem like a good plan. I'll adjust the patch so
>> that it continues to ignore errors in that case.
>
> Updated patch attached.
>

Patch looks good to me.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2017-05-07 08:21:28 Re: logical replication syntax (was DROP SUBSCRIPTION, query cancellations and slot handling)
Previous Message Bruce Momjian 2017-05-07 03:36:48 Re: PG 10 release notes