Hi Andy,
Yes important omissions:
Server version: 8.4.6
OS Windows Server 2003 Standard Ed :(
The work mem is 50mb.
I tried setting the work_mem to 500mb, but it didn't make a huge difference in
query execution time. But then again the OS disk caching is probably taking
over here.
Ok here's t
-Original Message-
From: Andy Colson [mailto:a...@squeakycode.net]
Sent: Monday, 17 January 2011 5:22 p.m.
To: Jeremy Palmer
Cc: pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Possible to improve query plan?
First, wow, those are long names... I had a hard time keeping track.
S
Hi Andy,
Yeah sorry about the long name, there are all generated by function as part of
a table versioning system. And yes I placed all possible indexes on the table
to see which would be used by the planner. In production I will drop the unused
indexes.
Yes simple drop the extra index :P I h
On 01/16/2011 09:21 PM, Jeremy Palmer wrote:
Hi all,
I've come to a dead end in trying to get a commonly used query to perform
better. The query is against one table with 10 million rows. This table has
been analysed. The table definition is:
CREATE TABLE version_crs_coordinate_revision
(
Hi all,
I've come to a dead end in trying to get a commonly used query to perform
better. The query is against one table with 10 million rows. This table has
been analysed. The table definition is:
CREATE TABLE version_crs_coordinate_revision
(
_revision_created integer NOT NULL,
_revision_
