Re: [JDBC] Support for JDBC setQueryTimeout, et al.
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Dimitri Fontaine <dimitri@2ndQuadrant.fr>, 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:22:51Z
Lists: pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes: >> The whole problem with search_path and role is very frustrating. We've >> taken to just hacking things to be dynamic SQL whenever it's >> role-specific, but that's a really poor solution. I wonder if it would >> be possible to have the function and prepare'd plan caches be key'd off >> of the search_path and role too..? So if you change one of those you >> end up having to re-plan it, but then that's also cached, etc.. FWIW, I can see the point of making cached plan lookup be search-path-specific. But why does the active role need to factor into it? regards, tom lane