Horton

Re: incorrect handling of the timeout in pg_receivexlog

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

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Fujii Masao <masao.fujii@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-06-05T13:47:06Z
Lists: pgsql-hackers 
Magnus Hagander <magnus@hagander.net> writes:
> On Tue, Jun 5, 2012 at 3:36 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
>> We discussed this before and reached consensus not to use %m :)
>> http://archives.postgresql.org/pgsql-hackers/2011-01/msg01674.php

> :-) there goes my memory.

> That said, we're using %m in a fairly large number of places already,
> but they're mostly in the backend. I guess we're safe there.

It should only appear in elog/ereport calls; if there are any in bare
printfs, they are wrong, just as Fujii-san says.  Frontend or backend
doesn't matter.

			regards, tom lane