Re: Prepared statements and suboptimal plans

* Royce Ausburn (royce(dot)ml(at)inomial(dot)com) wrote:
> > Tom just mentioned that 9.1 will be able to re-plan parameterized prepared statements, so this issue will go away. In the mean time you can only really use the standard workaround of setting the prepare theshold to 0 to disable server-side prepare, so you can continue to use JDBC prepared statements and have the driver do the parameter substitution for you.
>
> Thanks Craig -- that trick helps a lot.

You might also be able to bump up work_mem by a fair bit to get PG to
use a hashagg instead of groupagg/sort, even though its estimate is way
off. That's what I've done in the past for similar situations and it's
worked well. I'd recommend increasing it for just this query and then
resetting it (assuming you don't just drop the connection, in which case
you don't need to reset it since a new connection will get the default).

Thanks,

Stephen