Re: Oddity in handling of cached plans for FDW queries
От | Etsuro Fujita |
---|---|
Тема | Re: Oddity in handling of cached plans for FDW queries |
Дата | |
Msg-id | 9b21f8e3-13c7-5b9a-7f35-edddef21c181@lab.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: Oddity in handling of cached plans for FDW queries (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Oddity in handling of cached plans for FDW queries
|
Список | 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
В списке pgsql-hackers по дате отправления: