Re: Add support for logging the current role

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add support for logging the current role
Date: 2011-01-17 16:44:09
Message-ID: 1295282505-sup-8471@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Tom Lane's message of sáb ene 15 00:34:40 -0300 2011:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:

> > What about something other than
> > version_x_y? I could maybe see having a 'default' and an 'all'
> > instead.. Then have the default be what we have currently and 'all' be
> > the full list I'm thinking about.
>
> If "default" always means what it means today, I can live with that.
> But if the meaning of "all" changes from version to version, that seems
> like a royal mess. Again, I'm concerned that an external tool like
> pgfouine be able to make sense of the value without too much context.
> If it doesn't know what some of the columns are, it can just ignore them
> --- but a magic summary identifier that it doesn't understand at all is
> a problem.

Maybe if we offered a way for the utility to find out the field list
from the magic identifier, it would be enough.

(It would be neat to have magic identifiers for "terse", "verbose",
etc, that mimicked the behavior of client processing)

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-01-17 16:46:04 Re: Replication logging
Previous Message Tom Lane 2011-01-17 16:43:23 Re: Moving test_fsync to /contrib?