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: Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com>, 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-06-07 15:20:40
Message-ID: CAA4eK1+ELqcypmhzSd5LO9Y1XyFiVXpaPk7enNkA5yHQKdWZDg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 3, 2017 at 1:03 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Jun 2, 2017 at 3:48 AM, Rafia Sabih
> <rafia(dot)sabih(at)enterprisedb(dot)com> wrote:
>
> I don't see how to do that. It could possibly be done with the TAP
> framework, but that exceeds my abilities.
>
> Here's an updated patch with a bunch of cosmetic fixes, plus I
> adjusted things so that do_sql_command() is more interruptible. I
> tested it manually and it seems to work OK. I'll commit and
> back-patch this version, barring objections or further suggestions for
> improvement.
>

No objections from me, updated patch looks good.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2017-06-07 15:45:20 Re: BUG #14682: row level security not work with partitioned table
Previous Message Robert Haas 2017-06-07 15:02:06 Re: postgres_fdw cost estimation defaults and documentation