Horton

Re: Add support for logging the current role

Stephen Frost <sfrost@snowman.net>

View thread
From: Stephen Frost <sfrost@snowman.net>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, Noah Misch <noah@leadboat.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-02-11T15:59:46Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add support for an application_name parameter, which is displayed in

  2. Make CSV column ordering a bit more logical.

  3. Extend the format of CSV logs to include the additional information supplied

  4. Add virtual transaction IDs to CSVLOG output, so that messages coming from

  5. Provide for logfiles in machine readable CSV format. In consequence, rename

* Robert Haas (robertmhaas@gmail.com) wrote:
> Yeah.  The root cause of this problem is that the way psql handles
> tabular output with a few very wide rows stinks.

True, but it would be kinda nice to support multi-line configuration
variables.  I still vote for that being "not required to get this patch
in", but it's certainly something we could do later.  Of course, you do
have to ask yourself what having \n's in log_line_prefix would mean in
the config file..

	Thanks,

		Stephen