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

From Heikki Linnakangas
Subject Re: Walsender doesn't process options passed in the startup packet
Date
Msg-id 4C8A0E7E.3090801@enterprisedb.com
Whole thread Raw
In response to 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  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
On 10/09/10 13:17, Fujii Masao wrote:
> Hi,
>
> I found walsender didn't process options (e.g., application_name
> in primary_conninfo) passed in the startup packet. The cause is
> that walsender doesn't execute process_postgres_switches() and
> SetConfigOption() in InitPostgres().
>
> The attached patch fixes this bug.

Hmm, should walsender call InitializeClientEncoding too? It affects 
error messages. And what about per-user settings in pg_db_role_setting?

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Walsender doesn't process options passed in the startup packet
Next
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session