From: Tom Lane <tgl@sss.pgh.pa.us>
To: Laurent Raufaste <analogue@glop.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: PG planning randomly ?
Date: Tue, 26 Feb 2008 12:59:39 -0500
Message-ID: <5296.1204048779@sss.pgh.pa.us> (raw)
In-Reply-To: <669dc9710802260912y7fe58f9epe42fe7eb360119d8@mail.gmail.com>
References: <669dc9710802260719h61d846b3hd50b7f547bcb82c3@mail.gmail.com>
<3637.1204043502@sss.pgh.pa.us>
<669dc9710802260912y7fe58f9epe42fe7eb360119d8@mail.gmail.com>
"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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, analogue@glop.org
Subject: Re: PG planning randomly ?
In-Reply-To: <5296.1204048779@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox