| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Walsender doesn't process options passed in the startup packet |
| Date: | 2010-09-13 03:32:26 |
| Message-ID: | 20853.1284348746@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> On Fri, Sep 10, 2010 at 9:56 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-09-13 04:55:30 | Commitfest September 2010 Plans and Call for Reviewers |
| Previous Message | Fujii Masao | 2010-09-13 03:14:53 | Re: Walsender doesn't process options passed in the startup packet |