Re: Patch: psql \whoami option

Поиск
Список
Период
Сортировка
От Magnus Hagander
Тема Re: Patch: psql \whoami option
Дата
Msg-id 9837222c1001270201h17377093nf8a722f7f30bc5a4@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Patch: psql \whoami option  (Josh Berkus <josh@agliodbs.com>)
Ответы Re: Patch: psql \whoami option  (Martin Atukunda <matlads@gmail.com>)
Re: Patch: psql \whoami option  (David Christensen <david@endpoint.com>)
Список pgsql-hackers
2010/1/27 Josh Berkus <josh@agliodbs.com>:
> On 1/26/10 3:24 PM, David Christensen wrote:
>> -hackers,
>>
>> In the spirit of small, but hopefully useful interface improvement
>> patches, enclosed for your review is a patch for providing psql with a
>> \whoami command (maybe a better name is \conninfo or similar).  Its
>> purpose is to print information about the current connection, by default
>> in a human-readable format.  There is also an optional format parameter
>> which currently accepts 'dsn' as an option to output the current
>> connection information as a DSN.

On a first note, it seems like the check for the parameter "dsn" isn't
"complete". Without testing it, it looks like it would be possible to
run "\whoami foobar", which should give an error.


> oooh, I could really use this.  +1 to put it in 9.1-first CF.
>
> however, \conninfo is probably the better name.  And what about a

+1 on that name.

> postgresql function version for non-psql connections?

How could that function possibly know what the connection looks like
from the client side? Think NAT, think proxies, think connection
poolers.

-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Leonardo F
Дата:
Сообщение: Re: About "Our CLUSTER implementation is pessimal" patch
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: testing cvs HEAD - HS/SR - missing file