Prev: Endgame for all those SELECT FOR UPDATE changes: fix plan node order
Next: xpath_table equivalent
From: Tom Lane on 27 Oct 2009 17:09
Tim Landscheidt <tim(a)tim-landscheidt.de> writes:
> log file entries from running vacuumdb are "double-spaced",
> as vacuumdb ends the commands with ";\n" (cf. attached mini-
> patch). Is there a deeper meaning in that, or could it be
> trimmed?

There are a LOT of clients that tend to send queries with trailing
newlines; I'm pretty sure that both pg_dump and psql have instances of
that, for example. If we were to do something about this, which I'm
entirely unconvinced we should, it'd be better to strip trailing
whitespace from the logged query inside the backend.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: Endgame for all those SELECT FOR UPDATE changes: fix plan node order
Next: xpath_table equivalent