Horton

Re: Add support for logging the current role

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: Stephen Frost <sfrost@snowman.net>, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-01-14T22:10: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/14/2011 05:04 PM, Aidan Van Dyk wrote:
> If there is going to be any change, how about using fixed columns (an
> possibly allowing them to be empty for stuff that's expensive to
> create/write), but adding a 1st column that contains a "version"
> identifyer.  And to make it easy, maybe the PG major version as the
> version value.
>
> If the 1st column is always the version,  tools can easily know if
> they understand all the columns (and what order they are in) and it'
> easy to write a "conversion" that strips/re-aranges columns from a
> newer CVS dump to match an older one if you have tools that don't know
> about newer column layouts..
>
>


The whole point of having CSV logs is so you can load them into a 
database table without needing preprocessing tools. So I'm not going to 
be very receptive to changes that are predicated on using such tools.

cheers

andrew