Re: user connection properties

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <isabella(dot)ghiurea(at)nrc-cnrc(dot)gc(dot)ca>
Cc: "Scott Mead" <scott(dot)lists(at)enterprisedb(dot)com>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: user connection properties
Date: 2009-07-16 19:00:22
Message-ID: 4A5F32760200002500028842@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Isabella Ghiurea <isabella(dot)ghiurea(at)nrc-cnrc(dot)gc(dot)ca> wrote:

> I don't think optional is the right word,.

The issue is that the server has no clue what the application is
beyond what the client sends over the wire, so the server must trust
the client to tell it something useful. There is a lot of code out
there which doesn't set this (so far nonexistent) connection property,
and I'm sure that breaking all of that code is not an option. Hence,
if we add it, it will be optional.

> This information should be collected in one of the internal table,
> next to client's host ip and user name .

This would probably show up in pg_stat_activity somewhere.

> BTW: I don't know to much about PG 's " feature wish list " , if
> we get more feedback from some of the Gurus we can add this one
> to the list.

There is a TODO list.

http://wiki.postgresql.org/wiki/Todo

I'll suggest this be added.

-Kevin

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Marlowe 2009-07-16 19:03:33 Re: commit within function
Previous Message Carol Walter 2009-07-16 18:23:31 Re: Old version?