|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Amit Langote <amitlangote09(at)gmail(dot)com>|
|Cc:||Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, 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.|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> On Mon, Apr 4, 2016 at 11:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> A related issue, now that I've seen this example, is that altering
>> FDW-level or server-level options won't cause a replan either. I'm
>> not sure there's any very good fix for that. Surely we don't want
>> to try to identify all tables belonging to the FDW or server and
>> issue relcache invals on all of them.
> Hm, some kind of PlanInvalItem-based solution could work maybe?
Hm, so we'd expect that whenever an FDW consulted the options while
making a plan, it'd have to record a plan dependency on them? That
would be a clean fix maybe, but I'm worried that third-party FDWs
would fail to get the word about needing to do this.
regards, tom lane
|Next Message||Jesper Pedersen||2016-04-04 15:25:56||Re: Speed up Clog Access by increasing CLOG buffers|
|Previous Message||Tom Lane||2016-04-04 15:21:15||Re: [PROPOSAL] Client Log Output Filtering|