Message-ID: <B0DF162C81E84748A71F9FA153ED7BA2@andrusnotebook>
From: "Andrus" <kobruleht2@hot.ee>
To: "Richard Huxton" <dev@archonet.com>
Cc: <mweilguni@sime.com>,
	<pgsql-performance@postgresql.org>
References: <gg9pg5$1edv$1@news.hub.org> <492A7591.3000700@archonet.com>
	<C2F601D897194339A0D2327188C781D6@andrusnotebook>
	<492D27C8.7090206@archonet.com>
	<4936D68EF8C84087BBB9212C4019D5D8@andrusnotebook>
	<492D9E78.9080902@archonet.com>
In-Reply-To: <492D9E78.9080902@archonet.com>
Subject: Re: Increasing pattern index query speed
Date: Wed, 26 Nov 2008 21:40:30 +0200
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="windows-1257";
	reply-type=original
Content-Transfer-Encoding: 7bit

Richard,

> And the results were?

Results are provided in bottom of the message to which you replied.

> One problem at a time. Let's get the pattern-matching speed problems on
> your live server sorted, then we can look at different queries.

First message in this thread described the issue with query having
additional condition

AND dok.kuupaev BETWEEN '2008-11-21' AND  '2008-11-21'

It seems that this problem occurs when pattern matching and BETWEEN
conditions are used in same query.

According to Scott Garey great recommendation I added

ALTER TABLE rid ALTER COLUMN toode SET STATISTICS 1000;

This fixes testcase in live server, see my other message.
Is it OK to run

ALTER TABLE rid ALTER COLUMN toode SET STATISTICS 1000

in prod database or should I try to decrease 1000 to smaller value ?
rid is big increasing table and is changed frequently, mostly by adding 
rows.

Andrus.