Re: BUG #8291: postgres_fdw does not re-read USER MAPING after change. - Mailing list pgsql-bugs

From Bernd Helmle
Subject Re: BUG #8291: postgres_fdw does not re-read USER MAPING after change.
Date
Msg-id 01D9AE3B275492A46A0F06E3@localhost
Whole thread Raw
In response to BUG #8291: postgres_fdw does not re-read USER MAPING after change.  (lalbin@fhcrc.org)
Responses Re: BUG #8291: postgres_fdw does not re-read USER MAPING after change.
List pgsql-bugs

--On 9. Juli 2013 22:05:20 +0000 lalbin@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
Attachment

pgsql-bugs by date:

Previous
From: Alex Lai
Date:
Subject: Unable to handle error in plperl
Next
From: "Albin, Lloyd P"
Date:
Subject: Re: BUG #8291: postgres_fdw does not re-read USER MAPING after change.