| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Scott Mead" <scott(dot)lists(at)enterprisedb(dot)com>, <isabella(dot)ghiurea(at)nrc-cnrc(dot)gc(dot)ca> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: user connection properties |
| Date: | 2009-07-16 15:41:54 |
| Message-ID: | 4A5F03F2020000250002883C@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> wrote:
> Isabella Ghiurea <isabella(dot)ghiurea(at)nrc-cnrc(dot)gc(dot)ca> wrote:
>> From which internal tables/views I can get the user connection
>> application/job name ? (pg_stat _activity has the client ip
>> address only)
> Unlike Oracle, PG doesn't give you the remote application name.
Sybase ASE and Microsoft SQL Server both give the connecting
application a way to specify an application name, too. When that's
available, it can occasionally help sort out what's what. If we were
to add that, I assumed we'd want to make it optional (for
compatibility).
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Isabella Ghiurea | 2009-07-16 15:56:51 | Re: user connection properties |
| Previous Message | J. Carlos Muro | 2009-07-16 15:27:27 | Tests with switch of WAL segment files. |