On Fri, May 12, 2017 at 08:35:26PM +0300, Konstantin Knizhnik wrote: > > > On 12.05.2017 18:23, Bruce Momjian wrote: > >On Fri, May 12, 2017 at 10:50:41AM +0300, Konstantin Knizhnik wrote: > >>Definitely changing session context (search_path, date/time format, ...) may > >>cause incorrect behavior of cached statements. > >I wonder if we should clear the cache whenever any SET command is > >issued. > > Well, with autoprepare cache disabled on each set variable, alter system and > any slow utility statement > only one regression test is not passed. And only because of different error > message context:
Great. We have to think of how we would keep this reliable when future changes happen. Simple is often better because it limits the odds of breakage. > >>Actually you may get the same problem with explicitly prepared statements > >>(certainly, in the last case, you better understand what going on and it is > >>your choice whether to use or not to use prepared statement). > >> > >>The fact of failure of 7 regression tests means that autoprepare can really > >>change behavior of existed program. This is why my suggestion is to switch > >>off this feature by default. > >I would like to see us target something that can be enabled by default. > >Even if it only improves performance by 5%, it would be better overall > >than a feature that improves performance by 90% but is only used by 1% > >of our users. > > I have to agree with you here. Good. I know there are database systems that will try to get the most performance possible no matter how complex it is for users to configure or to maintain, but that isn't us. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
