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: Kevin Grittner <Kevin.Grittner@wicourts.gov>, Stephen Frost <sfrost@snowman.net>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, Noah Misch <noah@leadboat.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2011-02-11T16:26: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

Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Feb 11, 2011 at 10:34 AM, Kevin Grittner
> <Kevin.Grittner@wicourts.gov> wrote:
>> Should we abbreviate something there? max_pred_locks_per_tran,
>> maybe?

> 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.

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".

			regards, tom lane