Re: Add support for logging the current role
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, Noah Misch <noah@leadboat.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-02-11T16:33:23Z
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
* Tom Lane (tgl@sss.pgh.pa.us) wrote: > Robert Haas <robertmhaas@gmail.com> writes: > > If we're going to abbreviate transaction, I'd vote for txn over tran, > > but I think Stephen's point that this is already a lost cause may have > > some validity. Not sure what other people think. I agree w/ reducing that particular GUC a bit in size, but just to make it clear- that doesn't even come close to solving or fixing the 80-character terminal issue wrt 'show all;'... > Aren't we already using "xact" for that purpose in some user-visible > places? But personally I'd be happy with "max_pred_locks_per_transaction" > which gets the worst case down without being too obviously at variance > with "max_locks_per_transaction". Sounds good to me. The header length for show all would drop to only 206 characters (or so) with that change. If we offered a 'show all;' which didn't include 'description' and didn't have any settings longer than about 46 characters, *then* it'd fit on an 80-char terminal. Of course, if we had multi-line GUC support, we could put each field on a new line and each of those is well under 46 characters.. Thanks, Stephen