Re: Walsender doesn't process options passed in the startup packet

Fujii Masao <masao.fujii@gmail.com>

View thread

From: Fujii Masao <masao.fujii@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2010-09-13T05:10:22Z

Lists: pgsql-hackers

Attachments

startup_packet_options_and_walsender_v3.patch (application/octet-stream) patch v3

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