Re: Application name patch - v4 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Application name patch - v4
Date
Msg-id 4508.1259691922@sss.pgh.pa.us
Whole thread Raw
In response to Re: Application name patch - v4  (Marko Kreen <markokr@gmail.com>)
Responses Re: Application name patch - v4  (Marko Kreen <markokr@gmail.com>)
List pgsql-hackers
Marko Kreen <markokr@gmail.com> writes:
> If the pooler gets new connection with same username:database
> as some existing connection, but with different appname,
> what it is supposed to do?

Whatever it wants to.  People seem to be imagining that the appname
isn't under the control of the pooler.  It's a connection property,
remember?  It won't be set at all unless the pooler explicitly sets it
or allows it to be set.

I would imagine that typically a pooler would consider the whole
connection string as defining connection properties and so appname would
work the same as username or anything else, ie, you get shunted into
a different connection pool if you ask for a different appname.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Block-level CRC checks
Next
From: Heikki Linnakangas
Date:
Subject: Re: Hot Standby remaining issues