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

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Walsender doesn't process options passed in the startup packet
Date: 2010-09-10 10:54:54
Message-ID: 4C8A0E7E.3090801@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-09-10 12:45:46 Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session
Previous Message Fujii Masao 2010-09-10 10:17:36 Walsender doesn't process options passed in the startup packet