Re: postgres_fdw : altering foreign table not invalidating prepare statement execution plan.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
Cc: Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>,
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>,
Amit Langote <amitlangote09@gmail.com>,
Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-01-06T19:17:22Z
Lists: pgsql-hackers
Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp> writes: > On 2017/01/06 21:25, Ashutosh Bapat wrote: >> On Thu, Jan 5, 2017 at 2:49 PM, Etsuro Fujita >> <fujita.etsuro@lab.ntt.co.jp> wrote: >>> On 2017/01/03 15:57, Ashutosh Bapat wrote: >>>> The patch looks good to me, but I feel there are too many testscases. >>> I don't object to that, but (1) the tests I added wouldn't be that >>> time-consuming, and (2) they would be more expected to help find bugs, in >>> general, so I'd vote for keeping them. How about leaving that for the >>> committer's judge? >> Ok. Marking this as ready for committer. > Thanks! Pushed. I ended up simplifying the tests some, partly because I agreed it seemed like overkill, but mostly because they weren't testing the bug. The prepared statements that had parameters would have been replanned anyway, because plancache.c wouldn't have generated enough plans to decide if a generic plan would be ok. regards, tom lane
Commits
-
Invalidate cached plans on FDW option changes.
- e4380e4cf68a 9.4.11 landed
- c52d37c8b367 10.0 landed
- aaf12e577ee9 9.5.6 landed
- a8191800a6e6 9.3.16 landed
- 4103a2f200d6 9.6.2 landed