Skip site navigation (1) Skip section navigation (2)

Re: Application name patch - v4

From: Marko Kreen <markokr(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dave Page <dpage(at)pgadmin(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
Subject: Re: Application name patch - v4
Date: 2009-12-01 16:52:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 12/1/09, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dave Page <dpage(at)pgadmin(dot)org> writes:
> > On Tue, Dec 1, 2009 at 4:19 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>  >> I don't think that we need to bump the protocol version.  The real
>  >> alternative here would be that libpq sends a startup packet that
>  >> includes application_name, and if it gets an error back from that,
>  >> it starts over without the app name.
> > I looked (briefly) at doing that when we first ran into this
>  > suggestion. As you pointed out at the time, it seemed like that would
>  > require some fairly ugly hackery in fe-connect.c
> Perhaps, but at the time it wasn't apparent that issuing a separate SET
>  would create user-visible behavioral inconsistencies.  Now that we've
>  realized that, I think we should reconsider.
>  If people are agreed that double connect is a better alternative
>  I'm willing to go look at how to make it happen.

Is it supposed to work with pooling or not?

If the pooler gets new connection with same username:database
as some existing connection, but with different appname,
what it is supposed to do?


In response to


pgsql-hackers by date

Next:From: Marc G. FournierDate: 2009-12-01 17:51:14
Subject: Re: [CORE] EOL for 7.4?
Previous:From: Dave PageDate: 2009-12-01 16:51:47
Subject: Re: [CORE] EOL for 7.4?

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group