Re: Prepared Statement Query Planning

Oliver Jowett wrote:

Brett Henderson wrote:

It looks like you're using setFetchSize(). That forces use of a named statement regardless of prepareThreshold (we have to keep the statement and corresponding portal alive so we can do subsequent fetches, even if there are some other intervening queries, so we can't use the unnamed statement)

Yes, I'm currently using a fetch size of 10000.  I can't allow all results to be read at once because there can potentially be a huge number of results in the queries.  I've just tested it out, and sure enough leaving the fetch size at 0 prevents the use of named statements.