Re: raising the default prepareTheshold

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: raising the default prepareTheshold
Date: 2004-09-23 07:16:40
Message-ID: 41527858.6060909@opencloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Kris Jurka wrote:
>
> On Mon, 20 Sep 2004, Kris Jurka wrote:
>
>
>>At the same time do you think we should change the default fetchSize to
>>1000 or so? Even though it only works for FORWARD_ONLY ResultSets it
>>could reduce the number of complaints we see here without much penalty.
>>Previously the cursor implementation was more limiting by ruling out
>>server prepared statements.
>>
>
>
> Actually a little testing shows that a non-zero fetchSize implies using a
> named statement instead of the unnamed statement. So there will be some
> potentially negative planning differences, so I'm going to retract this
> suggestion.

Ah, this is because if we used the unnamed statement, the created portal
gets closed when the unnamed statement is reused. I forgot about that.

-O

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2004-09-23 07:16:48 Re: Detecting SQL_ASCII databases
Previous Message Kris Jurka 2004-09-23 07:09:33 Re: raising the default prepareTheshold