I've tried searching the documentation to answer this question but could
not find anything. When trying to choose the optimal fillfactor for an
index, what is important the number of times the row is updated or the
column indexed upon is updated? In my case each row is updated on
average about
Thank you! setting the protocolVersion=2 works with the newer driver.
I'm still puzzled as to why the prepareThreshold=0 doesn't force the
replan though.
On 2/26/07, Dave Cramer <[EMAIL PROTECTED]> wrote:
On 26-Feb-07, at 11:12 AM, Gene wrote:
> hi!
>
> I&#x
hi!
I've been having some serious performance issues with
postgresql8.2/hibernate/jdbc due to postgres reusing bad cached query
plans. It doesn't look at the parameter values and therefore does not
use any partial indexes.
After trying to set prepareThreshold=0 in the connection string which
did
arate
partitions/tablespaces for the two large tables and indexes?
Thanks
Gene
On 12/7/06, Shane Ambler <[EMAIL PROTECTED]> wrote:
>> One thing that is clear from what you've posted thus far is that you
>> are going to needmore HDs if you want to have any chance of fully
>
-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
-- Gene Hartcell: 443-604-2679
ill the transaction prevent that from occurring? I've done some testing and it seems to work but I could just get lucky so far and not lose any data :)
Thanks for any help,Gene
Thanks for the suggestion. Actually I went ahead and created a reverse
function using plpgsql, created an index using reverse column and now
my queries use "where reverse(column) like reverse('%2345') and it's
using the index like i hoped it would! Now if I could figure out how
to optimize like '
Is there any way to create a reverse index on string columns so that
queries of the form:
where column like '%2345';
can use an index and perform as fast as searching with like '2345%'?
Is the only way to create a reverse function and create an index using
the reverse function and modify querie
