Skip site navigation (1) Skip section navigation (2)

Re: Slow SQL lookup due to every field being listed inSORT KEY

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Mason Harding <mason(dot)harding(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Slow SQL lookup due to every field being listed inSORT KEY
Date: 2010-09-11 01:59:03
Message-ID: 20100911015903.GG26232@tamriel.snowman.net (view raw or flat)
Thread:
Lists: pgsql-performance
* Mason Harding (mason(dot)harding(at)gmail(dot)com) wrote:
> Hi all.  I Have the following query (tested in postgres 8.4 and 9.0rc1)

Can you provide \d output from all the tables involved..?

Also, what does the query plan look like w/o 'enable_seqscan=off' (which
is not a good setting to use...)?  Increasing work_mem is often a good
idea if your system can afford it based on the number/kind of queries
running concurrently.  Note that you can also increase that setting for
just a single role, single session, or even single query.

	Thanks,

		Stephen

In response to

pgsql-performance by date

Next:From: Tom LaneDate: 2010-09-11 02:00:38
Subject: Re: Slow SQL lookup due to every field being listed in SORT KEY
Previous:From: Mason HardingDate: 2010-09-10 22:35:17
Subject: Slow SQL lookup due to every field being listed in SORT KEY

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group