| From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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-21 07:30:46 |
| Message-ID: | 9b21f8e3-13c7-5b9a-7f35-edddef21c181@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016/07/16 6:25, Tom Lane wrote:
> 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.
I left that for future work, but I'm happy to have that in 9.6. Thanks
for improving and committing the patch!
One thing I'd like to discuss is GetUserMappingById/GetUserMappingId.
Though those functions aren't used in any places, I didn't take them
out, because I thought somebody else would need them someday. But
considering that user mapping OIDs now aren't available in RelOptInfos,
at least the former might be rather useless. Should we keep them in core?
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2016-07-21 07:49:11 | Re: PoC: Make it possible to disallow WHERE-less UPDATE and DELETE |
| Previous Message | Satoshi Nagayasu | 2016-07-21 05:12:31 | Re: DROP OWNED BY ... CACADE & "could not open relation with OID" error |