Horton

Re: [JDBC] Support for JDBC setQueryTimeout, et al.

Stephen Frost <sfrost@snowman.net>

View thread
From: Stephen Frost <sfrost@snowman.net>
To: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Radosław Smogura <rsmogura@softperience.eu>, Magnus Hagander <magnus@hagander.net>, David Fetter <david@fetter.org>, Kevin Grittner <Kevin.Grittner@wicourts.gov>, PG Hackers <pgsql-hackers@postgresql.org>, PostgreSQL JDBC List <pgsql-jdbc@postgresql.org>, robertmhaas@gmail.com
Date: 2010-10-15T20:14:40Z
Lists: pgsql-hackers 
Dimitri,

* Dimitri Fontaine (dimitri@2ndQuadrant.fr) wrote:
[... much useful info ...]

Thanks for all of that, I certainly appreciate it.

> By default pgbouncer maintains a different pool per database and role,
> so you should be partly covered here.

No, not really..  We have a single unprivileged account which is used
for login and then that account can 'set role' to other roles (of
course, we set it up so the login role *has* to set role to another user
to be able to do anything).  I doubt pgbouncer is going to switch pooler
connections on seeing a set role and I'm not really sure it'd make sense
for it to anyway.

	Thanks,

		Stephen