I realized that postgres_fdw is caching the connection, but when you have existing items that use the same USER MAPPING and do not cache it such as dblink you get inconsistency in implementation and this should be avoided.
Lloyd -----Original Message----- From: Bernd Helmle [mailto:maili...@oopsware.de] Sent: Wednesday, July 10, 2013 3:34 PM To: Albin, Lloyd P; pgsql-bugs@postgresql.org Subject: Re: [BUGS] BUG #8291: postgres_fdw does not re-read USER MAPING after change. --On 9. Juli 2013 22:05:20 +0000 lal...@fhcrc.org wrote: > I have found that if you change the password in the USER MAPPING, that > postgres_fdw will not use it unless the current password fails or you > close and re-open your postgres connection. I found this while testing > to see if the USER MAPPING's supports MD5 passwords and they appeared > to until the next day when I found that they no longer worked because > I had closed and re-opened my connection. > Hmm i don't think that's a bug. It's because the postgres_fdw caches the connection within your local session, reusing it for any subsequent foreign table access. > > The second error that I found is in the documentation of ALTER USER > MAPPING. It incorrectly says how to update a users password. > > It could be misread, i agree. Attached is a small doc patch to address this against HEAD. -- Thanks Bernd -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
