Re: Patch: psql \whoami option

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Martin Atukunda <matlads(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, David Christensen <david(at)endpoint(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch: psql \whoami option
Date: 2010-01-27 16:39:39
Message-ID: 8054.1264610379@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> 2010/1/27 Martin Atukunda <matlads(at)gmail(dot)com>:
>> How about using the psql prompt to convey this information?

> I think the idea is that if you do that, it'll be there all the time,
> potentially "crowding the space".

I had the same reaction as Martin. If you want this info all the time,
setting the prompt is the way to go. If you only want it occasionally,
you're probably more likely to remember other ways of getting the info
first (session_user, pg_stat_activity, etc etc). There may be some
use-case in between where another backslash command would be helpful,
but it seems a tad marginal to me. I don't object as long as it's not
overdesigned, but let's keep the bells and whistles to a minimum.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tim Bunce 2010-01-27 16:40:19 Re: Add on_perl_init and proper destruction to plperl [PATCH]
Previous Message Heikki Linnakangas 2010-01-27 16:38:00 Re: testing cvs HEAD - HS/SR - missing file