| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, 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-07 23:01:53 |
| Message-ID: | 6166.1518044513@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I spent a while reading through this today. I see a few decisions
> here or there that are debatable, in the sense that somebody else
> might have chosen to do it differently, but I don't see anything that
> actually looks wrong. So, committed.
The buildfarm's opinion of it is lower than yours. Just eyeballing
the failures, I'd say there was some naivete about the reproducibility
of tuple CTIDs across different platforms. Is there a good reason
these test cases need to print CTID?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2018-02-07 23:45:50 | Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem |
| Previous Message | Alvaro Herrera | 2018-02-07 22:57:30 | Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem |