Re: primary_conninfo missing from pg_stat_wal_receiver - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: primary_conninfo missing from pg_stat_wal_receiver
Date
Msg-id 20160629175041.GA121670@alvherre.pgsql
Whole thread Raw
In response to Re: primary_conninfo missing from pg_stat_wal_receiver  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: primary_conninfo missing from pg_stat_wal_receiver  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Fujii Masao wrote:
> On Wed, Jun 29, 2016 at 12:23 PM, Alvaro Herrera
> <alvherre@2ndquadrant.com> wrote:
> > Michael Paquier wrote:
> >> On Wed, Jun 29, 2016 at 6:42 AM, Alvaro Herrera
> >> <alvherre@2ndquadrant.com> wrote:
> >
> >> > I have already edited the patch following some of these ideas.  Will
> >> > post a new version later.
> >>
> >> Cool, thanks.
> >
> > Here it is.  I found it was annoying to maintain the function return
> > tupdesc in two places (pg_proc.h and the function code itself), so I
> > changed that too.
> 
> ISTM that pg_stat_wal_receiver can return the security-sensitive fields
> if it's viewed before walreceiver overwrites the conninfo in the shared memory
> with the obfuscated one.

Hmm, ouch.  Maybe we can set a flag once the conninfo has been
obfuscated, and put the function to sleep until the flag is set.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: primary_conninfo missing from pg_stat_wal_receiver
Next
From: Fujii Masao
Date:
Subject: Re: primary_conninfo missing from pg_stat_wal_receiver