Horton

Re: Add support for logging the current role

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephen Frost <sfrost@snowman.net>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-01-14T16:36:38Z
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


On 01/12/2011 08:59 PM, Tom Lane wrote:
>
> I'm not actually concerned about adding a few extra cycles to SET ROLE
> for this.  What bothered me more was the cost of adding another output
> column to CSV log mode.  That's not something you're going to be able to
> finesse such that only people who care pay the cost.
>
> 			

I think it's time to revisit the design of CSV logs again, now we have 
two or three releases worth of experience with it. It needs some 
flexibility and refinement.

cheers

andrew