|From:||Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>|
|To:||Fujii Masao <masao(dot)fujii(at)gmail(dot)com>|
|Cc:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Walsender doesn't process options passed in the startup packet|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 13/09/10 08:10, Fujii Masao wrote:
> On Mon, Sep 13, 2010 at 12:32 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Huh? walsender has no business applying any per-user or per-database
> 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.
Right, per-database settings clearly make no sense, but per-role
settings do. There isn't very many settings that make sense for
walsender, but client_encoding is one example. I agree it's not terribly
useful, but would be nice for the sake of completeness.
> What about leaving the capability to apply per-role settings as a TODO
Yeah, seems best at this point.
|Next Message||Heikki Linnakangas||2010-09-13 06:10:29||Re: Interruptible sleeps (was Re: CommitFest 2009-07: Yay, Kevin! Thanks, reviewers!)|
|Previous Message||Fujii Masao||2010-09-13 05:10:22||Re: Walsender doesn't process options passed in the startup packet|