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

From Tom Lane
Subject Re: Walsender doesn't process options passed in the startup packet
Date
Msg-id 20853.1284348746@sss.pgh.pa.us
Whole thread Raw
In response to Re: Walsender doesn't process options passed in the startup packet  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Walsender doesn't process options passed in the startup packet
List pgsql-hackers
Fujii Masao <masao.fujii@gmail.com> writes:
> On Fri, Sep 10, 2010 at 9:56 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
>> BTW, this issue seems to derive from the following commit.
>> http://archives.postgresql.org/pgsql-committers/2010-04/msg00175.php

>> it was previously using an untenable assumption that template1 would
>> always be available to connect to

> The above commit message shows that the updated patch is untenable too
> since it assumes the existence of the template1.

> Is there way to access to pg_db_role_setting without connecting to the
> specific database? If not, it's difficult for walsender to process the
> per-user settings since it's tied to no database.

Huh?  walsender has no business applying any per-user or per-database
settings.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Walsender doesn't process options passed in the startup packet
Next
From: David Fetter
Date:
Subject: Commitfest September 2010 Plans and Call for Reviewers