Re: pgsql: Change replication connection log format to allow for a database

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Simon Riggs <sriggs(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Change replication connection log format to allow for a database
Date: 2010-03-25 20:09:15
Message-ID: 20100325200915.GD4350@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Heikki Linnakangas wrote:
> Heikki Linnakangas wrote:
> > I'm afraid this doesn't translate well:
> >
> >> --- 222,232 ----
> >> */
> >> if (am_walsender)
> >> ereport(LOG,
> >> ! (errmsg("replication connection authorized: user=%s host=%s%s%s",
> >> ! port->user_name,
> >> ! port->remote_host, port->remote_port[0] ? " port=" : "",
> >> ! port->remote_port)));
> >> !
> >> else if (Log_connections)
> >> ereport(LOG,
> >> (errmsg("connection authorized: user=%s database=%s",
>
> Ok, I just realized that this was copy-pasted from BackendInitialize, so
> I guess it's OK as it is...

Actually it would be good to correct both per your previous suggestion.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Simon Riggs 2010-03-25 20:40:18 pgsql: Modify some new and pre-existing messages for translatability.
Previous Message Simon Riggs 2010-03-25 19:48:06 Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL