| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Oddity in handling of cached plans for FDW queries |
| Date: | 2016-07-15 21:25:09 |
| Message-ID: | 8993.1468617909@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> writes:
>> Here is a patch for that redesign proposed by you; reverts commits
>> fbe5a3fb73102c2cfec11aaaa4a67943f4474383 and
>> 5d4171d1c70edfe3e9be1de9e66603af28e3afe1, adds changes for that redesign
>> to the core, and adjusts the postgres_fdw code to that changes. Also, I
>> rearranged the postgres_fdw regression tests to match that changes.
> OK, I'll review this later today.
Pushed, after fooling around with it some more so that it would cover the
case we discussed where the join could be allowed if we restrict the plan
to be executed by the owner of a view used in the query.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-07-15 21:32:34 | Re: heap_xlog_lock forgets to reset HEAP_XMAX_INVALID |
| Previous Message | Alvaro Herrera | 2016-07-15 21:23:57 | Re: heap_xlog_lock forgets to reset HEAP_XMAX_INVALID |