Re: [BUGS] BUG #14738: ALTER SERVER for foregin servers not working - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] BUG #14738: ALTER SERVER for foregin servers not working
Date
Msg-id 6234.1499801954@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] BUG #14738: ALTER SERVER for foregin servers not working  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: [BUGS] BUG #14738: ALTER SERVER for foregin servers not working  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List pgsql-bugs
Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> writes:
> Horiguchi-san,
> On 2017/07/11 10:28, Kyotaro HORIGUCHI wrote:
>> I faintly recall such discussion was held aroud that time and
>> maybe we concluded that we don't do that but I haven't find such
>> a thread in pgsql-hackers..

> I mentioned it in my reply.  Here again:
> https://www.postgresql.org/message-id/20160405.184408.166437663.horiguchi.kyotaro%40lab.ntt.co.jp

The followup discussion noted that that approach was no good because it
would only close connections in the same session that had done the ALTER
SERVER.  I think the basic idea of marking postgres_fdw connections as
needing to be remade when next possible is OK, but we have to drive it
off catcache invalidation events, the same as we did in c52d37c8b.  An
advantage of that way is we don't need any new hooks in the core code.

Kyotaro-san, are you planning to update your old patch?
        regards, tom lane


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: [BUGS] PostgreSQL hot standby Hangs due to AccessExclusiveLock onpg_attribute or pg_type tables
Next
From: Bruno Richard
Date:
Subject: Re: [BUGS] PostgreSQL hot standby Hangs due to AccessExclusiveLock onpg_attribute or pg_type tables