On Wed, Nov 30, 2016 at 2:35 PM, Etsuro Fujita <fujita.ets...@lab.ntt.co.jp> wrote: > On 2016/11/30 17:53, Amit Langote wrote: >> >> On 2016/11/30 17:25, Etsuro Fujita wrote: >>> >>> Done. I modified the patch so that any inval in pg_foreign_server also >>> blows the whole plan cache. > > >> I noticed the following addition: >> >> + CacheRegisterSyscacheCallback(FOREIGNDATAWRAPPEROID, >> PlanCacheSysCallback, (Datum) 0); >> >> Is that intentional? I thought you meant only to add for >> pg_foreign_server. > > > Yes, that's intentional; we would need that as well, because cached plans > might reference FDW-level options, not only server/table-level options. I > couldn't come up with regression tests for FDW-level options in > postgres_fdw, though.
The patch looks good to me, but I feel there are too many testscases. Now that we have changed the approach to invalidate caches in all cases, should we just include cases for SELECT or UPDATE or INSERT or DELETE instead of each statement? -- Best Wishes, Ashutosh Bapat EnterpriseDB Corporation The Postgres Database Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
