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

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

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-09-13T03:32:26Z
Lists: 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