Re: Add support for logging the current role
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Robert Haas <robertmhaas@gmail.com>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-02-14T02:52:51Z
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 →
-
Add support for an application_name parameter, which is displayed in
- 8217cfbd9918 9.0.0 cited
-
Make CSV column ordering a bit more logical.
- 230e8962f3a4 8.3.0 cited
-
Extend the format of CSV logs to include the additional information supplied
- 3bf66d6f1c3a 8.3.0 cited
-
Add virtual transaction IDs to CSVLOG output, so that messages coming from
- 77c166ba6cf6 8.3.0 cited
-
Provide for logfiles in machine readable CSV format. In consequence, rename
- fd801f4faa8e 8.3.0 cited
Andrew, * Andrew Dunstan (andrew@dunslane.net) wrote: > See the discussion back around the the 8.1 release (IIRC) when we > added the HEADER option. I recall seeing it and not agreeing with it then. :) > >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. Having a 'throw away 1 line' option is just silly to me, but documenting it as "header" is worse. Water under the bridge at this point though. > 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. I agree it's work for 9.2. I could probably help with this if people agree that it should be done. Thanks, Stephen