| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Subject: | Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly |
| Date: | 2018-02-09 16:50:14 |
| Message-ID: | CA+TgmoaAQCn0+xh3JG2avn35Lukj2NVmhxVi7hE2CwzSUQ-5ag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Feb 9, 2018 at 5:24 AM, Etsuro Fujita
<fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> I tried to reproduce that in my environment, but I couldn't. On reflection
> I think an easy and reliable way to address that concern is to use local
> stats on foreign tables. Attached is a patch for that.
Me neither. I just ran the postgres_fdw regression tests 713 times in
a row without a failure. Tom, since you seem to be able to reproduce
the problem locally, could you have a look at this proposed fix?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-09 18:33:08 | Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly |
| Previous Message | Andres Freund | 2018-02-09 16:30:49 | Re: CALL stmt, ERROR: unrecognized node type: 113 bug |