Re: Add support for logging the current role
Stephen Frost <sfrost@snowman.net>
From: Stephen Frost <sfrost@snowman.net>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-02-17T15:51:32Z
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) wrote: > Ugg, wait a minute. This not only adds %U; it also changes the > behavior of %u, which I don't think we've agreed on. Also, emitting > 'none' when not SET ROLE has been done is pretty ugly. I'm back to > thinking we need to push this out to 9.2 and take more time to think > about this. As I explained in various commit logs and, as I recall, when I first posted about it, the behavior change for %u could only come about when someone used 'SET SESSION AUTHORIZATION', which requires superuser privileges. It makes more sense to me for 'user_name' to be equivilant to 'SESSION USER', but it's really not that big a deal either way. Guess I had foolishly thought that people were alright with it by lack of any comments on it. :( Does anyone else want to chime in on this? I actually came across that problem because the documentation was poor regarding exactly what that column meant. If we actually want it to be "the name that the user first used to authenticate to the system with", then let's update the documentation accordingly and we can remove those changes. Thanks, Stephen