Horton

Re: Add support for logging the current role

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Stephen Frost <sfrost@snowman.net>
Cc: Robert Haas <robertmhaas@gmail.com>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-02-14T00:28:01Z
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 02/13/2011 08:26 AM, Stephen Frost wrote:
> This would be called a 'header' in most typical CSV scenarios.
> Unfortunately, last I checked (maybe it's changed?), COPY w/ HEADER just
> throws the header away instead of doing anything useful with it.  If it
> actually used the header to build the column list, then adding a header
> would be sufficient, provided all the necessary fields are in the table.

See the discussion back around the the 8.1 release (IIRC) when we added 
the HEADER option.

> If I wanted something to throw away the first record of a file before
> loading it, I'd use tail.
>

The whole point of us having direct CSV import is to minimise the 
requirement for preprocessing.

That said, I think there's probably a good case for an option to use the 
header line as a column list. I know of at least one application I have 
written that could benefit from it. But that's work for 9.2 or later.

cheers

andrew