On 2014-05-16 14:02:44 -0400, Tom Lane wrote:
> Andres Freund <and...@2ndquadrant.com> writes:
> > elog.c's log_line_prefix() processes %d with:
> > case 'd':
> > if (MyProcPort)
> > {
> > const char *dbname = MyProcPort->database_name;
>
> > if (dbname == NULL || *dbname == '\0')
> > dbname = _("[unknown]");
> > if (padding != 0)
> > appendStringInfo(buf, "%*s", padding, dbname);
>
> Not directly related to your gripe, but: where did this "padding" logic
> come from, and what prevents it from creating invalidly-encoded output by
> means of truncating multibyte characters in the middle?
Isn't that syntax just the *minimal* width?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
