Re: Walsender doesn't process options passed in the startup packet - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Walsender doesn't process options passed in the startup packet
Date
Msg-id AANLkTim1CnwOcBccRAu52GSrK7XvewGq=PmD1SWyZJ8Z@mail.gmail.com
Whole thread Raw
In response to Re: Walsender doesn't process options passed in the startup packet  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Walsender doesn't process options passed in the startup packet  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: Walsender doesn't process options passed in the startup packet  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Mon, Sep 13, 2010 at 12:32 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Huh?  walsender has no business applying any per-user or per-database
> settings.

Okay. I got rid of the access to pg_db_role_setting from the patch.
I attached the updated version, which makes walsender process the
options passed in the startup packet, apply PostAuthDelay and initialize
client encoding.

OTOH, I can believe that some people would create a dedicated role for
replication and configure the parameters for replication on the role.
What about leaving the capability to apply per-role settings as a TODO
item?

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment

pgsql-hackers by date:

Previous
From: KaiGai Kohei
Date:
Subject: Re: security label support, revised
Next
From: Heikki Linnakangas
Date:
Subject: Re: Walsender doesn't process options passed in the startup packet