--- On Fri, 12/2/11, David Johnston <polobo@xxxxxxxxx> wrote: > -------------------------------------------------------- > > Can you wrap the query into an SQL or PL/pgSQL function so > that, at least, > then planner will not be able to see the embedded plan info > in the outer > queries? You use-case may allow you to create one or > more VIEWs wrapping > the function call with pre-determined parameters so that > you do not lose the > ability to write simple select queries without the need for > explicit > function calls. > > No idea how that would impact the planner for the other > queries but maybe > worth a try while waiting for someone more knowledgeable > than myself to > respond. I had actually considered this...because you can define what the 'row estimate' is for a function....except in my case, I have some dynamic inputs that would change what those estimates would need to be. Thanks for the help though! -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general