From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Eric Ridge <ebr(at)tcdi(dot)com> |
Cc: | Pgsql-General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ps output and postgres |
Date: | 2004-02-12 03:00:24 |
Message-ID: | 200402120300.i1C30O001544@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Eric Ridge wrote:
> I like how postgres backends modify the 'command' display in a (unix)
> process listing to show what database they are connected to, and the
> query being executed.
>
> Has any thought been put into being able to make this configurable per
> backend connection (maybe via a SET variable)? I'm thinking it would
> be cool if a user process could provide its own status there,
> identifying application-specific information. Similar to how Java
> let's you set the "name" of a Thread (which sadly doesn't appear in a
> process listing, but oh well).
>
> I realize this could open up some security concerns by allowing us to
> expose more information than we should, but for those of us that want
> to shoot ourselves in the foot, it might be a useful feature.
No one really has thought of that before. We could do it, though there
are admin reasons for restricting that ability. If we said only
superusers could change it, it wouldn't be very useful. It would be
cool if SET could change it, but it seems that would make it pretty
useless for administrator usage.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-02-12 03:14:54 | Re: Is a capital letters title for this ML blocked? |
Previous Message | Troy Campano | 2004-02-12 02:05:52 | Re: Oracle SQLNet on same server as Postgres |