| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: postgres_fdw : altering foreign table not invalidating prepare statement execution plan. |
| Date: | 2016-11-30 08:53:46 |
| Message-ID: | e4e81c7a-8f0f-9a26-07d1-91da5f4aa130@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fujita-san,
On 2016/11/30 17:25, Etsuro Fujita wrote:
> On 2016/11/22 15:24, Etsuro Fujita wrote:
>> On 2016/11/22 4:49, Tom Lane wrote:
>
>>> OK, please update the patch to handle those catalogs that way.
>
>> Will do.
>
> Done. I modified the patch so that any inval in pg_foreign_server also
> blows the whole plan cache.
Thanks for updating the patch and sorry that I didn't myself.
I noticed the following addition:
+ CacheRegisterSyscacheCallback(FOREIGNDATAWRAPPEROID,
PlanCacheSysCallback, (Datum) 0);
Is that intentional? I thought you meant only to add for pg_foreign_server.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2016-11-30 09:05:44 | Re: postgres_fdw : altering foreign table not invalidating prepare statement execution plan. |
| Previous Message | Fabien COELHO | 2016-11-30 08:47:20 | Re: PSQL commands: \quit_if, \quit_unless |