Skip site navigation (1) Skip section navigation (2)

Re: add support for logging current role (what to review?)

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: add support for logging current role (what to review?)
Date: 2011-06-28 18:13:36
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tue, Jun 28, 2011 at 09:15, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Anyway, if we are going to insist on rewriting substantial chunks of
> the logging infrastructure before doing this, we at least need to
> reach some agreement on what would be an acceptable outcome - and then
> let Stephen code that up as a separate patch, submit it, get it
> committed, and then do this on top of that.  Or we can just decide
> that adding one relatively minor field to the text format output is
> not worth knocking over the applecart for.

Well, one of the reasons I picked up this patch is its a feature *I*
want. I remember being quite surprised at the role csv logging reports
when i switched to it. I was logging everything so I have on occasion
had to find a SET ROLE and follow the session... its quite annoying

I think if Stephen was proposing 10 fields, or if there was a list of
fields we were planning on adding in the next release or 3, it might
be worth re-factoring. I know of no such list, and I think this field
useful/important enough that people who are using csv logging would
want it anyway. +1 on just tacking on the field and causing a flag day
for csv users.

In response to


pgsql-hackers by date

Next:From: Martin PihlakDate: 2011-06-28 18:14:44
Subject: Re: libpq SSL with non-blocking sockets
Previous:From: Robert HaasDate: 2011-06-28 18:11:11
Subject: Re: Avoid index rebuilds for no-rewrite ALTER TABLE ALTER TYPE

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group