| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(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-06 17:11:58 |
| Message-ID: | CA+TgmoamON2js4EjQzJhP7Pzq8On0n9dT4bHPJsozCUHq4AnVQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| improve-pgfdw-abort-behavior-v2.patch | application/x-patch | 14.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-05-06 17:15:25 | Re: Draft release notes for next week's back-branch releases |
| Previous Message | Tom Lane | 2017-05-06 17:01:03 | Re: "CURRENT_ROLE" is not documented |