Re: Add support for logging the current role
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Stephen Frost <sfrost@snowman.net>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-02-17T00:42:50Z
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
Robert Haas <robertmhaas@gmail.com> writes: >>> On Tue, Feb 15, 2011 at 1:02 PM, Stephen Frost<sfrost@snowman.net> wrote: >>>> I believe the suggestion that Robert and I were talking about above was >>>> to just unilatterally change the CSV log file output format to include >>>> current_role. No header lines, no variable output format, etc. > OK. If no one objects further, Stephen and I will make that happen. > Otherwise: he's dead, Jim. I can't remember at the moment: have we changed the CSV format in any releases since it was first created? And if so, did anyone complain? If there's precedent showing this isn't going to be a problem for CSV users, I won't object. Otherwise I think that we should try to have just one flag day for them, not two. regards, tom lane