| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Radosław Smogura <rsmogura(at)softperience(dot)eu>, Magnus Hagander <magnus(at)hagander(dot)net>, David Fetter <david(at)fetter(dot)org>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL JDBC List <pgsql-jdbc(at)postgresql(dot)org>, robertmhaas(at)gmail(dot)com |
| Subject: | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |
| Date: | 2010-10-15 20:14:40 |
| Message-ID: | 20101015201440.GT26232@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
Dimitri,
* Dimitri Fontaine (dimitri(at)2ndQuadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-15 20:22:51 | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |
| Previous Message | Dimitri Fontaine | 2010-10-15 20:03:35 | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-10-15 20:22:51 | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |
| Previous Message | Dimitri Fontaine | 2010-10-15 20:03:35 | Re: [JDBC] Support for JDBC setQueryTimeout, et al. |