Prev: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
Next: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will
From: Tom Lane on 6 Jul 2010 17:41
I grow weary of mopping up after pgindent, as in
http://archives.postgresql.org/pgsql-committers/2010-07/msg00069.php

The problem evidently is that pgindent hasn't heard of wide character
constants. No doubt the best fix would be to teach it about them;
but given that we seem to have next to no use for such constants,
I'm dubious that it's worth the trouble. I suggest that it might be
best to replace these usages of L'\0' by plain scalar 0. Does anyone
think that wouldn't work or is too grotty?

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: TRUNCATE+COPY optimization and --jobs=1 in pg_restore
Next: [COMMITTERS] pgsql: Add note that using PL/Python 2 and 3 in the same session will