From: | Henk van Lingen <H(dot)G(dot)K(dot)vanLingen(at)uu(dot)nl> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Forcing the right queryplan |
Date: | 2010-09-10 08:27:35 |
Message-ID: | 20100910082735.GA32291@uu.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-novice |
On Thu, Sep 09, 2010 at 11:16:36AM -0400, Tom Lane wrote:
> Henk van Lingen <H(dot)G(dot)K(dot)vanLingen(at)uu(dot)nl> writes:
> > On Thu, Sep 09, 2010 at 10:50:52AM -0400, Tom Lane wrote:
> >>>> Well, there's your problem: the planner is off by a factor of about 500
> >>>> on its estimate of the number of rows matching this query, and that's
> >>>> what's causing it to pick the wrong plan. What you need to look into
> >>>> is getting that estimate to be more in sync with reality. Probably
> >>>> increasing the stats target for the message column would help.
>
> > But how can I get sane estimates for syslog data? Some searchstrings will
> > result in only a few hits, others in thousands of records or more.
>
> That's what ANALYZE is for ...
Yes, off course. But I don't see how the most_common_vals & freqs and the
histogram_bounds for a text field with syslog data make any sense when
doing doing a search for a substring. Increasing the number of entries in
those stats lists doesn't make any sense also, i presume.
Those stats should be based on analysis of the to_tsvector index, to have
any meaning, i think.
Today I will look into the multicolumn index suggestion.
Regards,
--
Henk van Lingen, ICT-SC Netwerk & Telefonie, (o- -+
Universiteit Utrecht, Jenalaan 18a, room 0.12 /\ |
phone: +31-30-2538453 v_/_ |
http://henk.vanlingen.net/ http://www.tuxtown.net/netiquette/
From | Date | Subject | |
---|---|---|---|
Next Message | Arjen Nienhuis | 2010-09-10 09:04:04 | Re: Forcing the right queryplan |
Previous Message | Scott Marlowe | 2010-09-10 03:31:02 | Re: postgres patch for autovacuum error in postgres |
From | Date | Subject | |
---|---|---|---|
Next Message | Mladen Gogala | 2010-09-10 08:49:46 | Transactional issue that begs for explanation |
Previous Message | Thom Brown | 2010-09-10 08:22:13 | Re: Postgresql & Deadlocks |