Re: PG planning randomly ? - Mailing list pgsql-performance

From Tom Lane
Subject Re: PG planning randomly ?
Date
Msg-id 5296.1204048779@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG planning randomly ?  ("Laurent Raufaste" <analogue@glop.org>)
Responses Re: PG planning randomly ?  ("Laurent Raufaste" <analogue@glop.org>)
List pgsql-performance
"Laurent Raufaste" <analogue@glop.org> writes:
> 2008/2/26, Tom Lane <tgl@sss.pgh.pa.us>:
>> If it's 8.2 or later then increasing the stats target for _comment.path
>> to 100 or more would likely help.

> I'm using PG 8.2.4.
> We are using 100 as default_statistics_target by default and all our
> column are using this value:

Hmm, that ought to be enough to activate the better selectivity
estimator.

Unless ... did you update this database from a pre-8.2 DB that already
had contrib/ltree in it?  If so, did you just load the existing old
definition of ltree as part of your dump, or did you install 8.2's
version fresh?  I'm wondering if you have a definition of operator <@
that doesn't specify the new selectivity estimator.  Please try a
pg_dump -s and see what it shows as the definition of <@.

            regards, tom lane

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: LISTEN / NOTIFY performance in 8.3
Next
From: "Laurent Raufaste"
Date:
Subject: Re: PG planning randomly ?