Re: [HACKERS] Support for JDBC setQueryTimeout, et al. - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: [HACKERS] Support for JDBC setQueryTimeout, et al.
Date
Msg-id 11068.1287174171@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Support for JDBC setQueryTimeout, et al.  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: [HACKERS] Support for JDBC setQueryTimeout, et al.  (Stephen Frost <sfrost@snowman.net>)
List pgsql-jdbc
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

pgsql-jdbc by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [HACKERS] Support for JDBC setQueryTimeout, et al.
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] Support for JDBC setQueryTimeout, et al.