Re: optimizing query

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Chantal Ackermann <chantal(dot)ackermann(at)biomax(dot)de>
Cc: <pgsql-general(at)postgresql(dot)org>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: optimizing query
Date: 2003-01-23 15:05:28
Message-ID: 20030123070120.Y11731-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-performance


On Thu, 23 Jan 2003, Chantal Ackermann wrote:

> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Postgres Version: 7.3.1
> CPU: 1666.767 MHz
> RAM: 2070492 kB
> shmmax/shmall: 1048576000
>
> postgresql.conf:
> shared_buffers: 121600
> max_connections: 64
> max_fsm_relations = 200
> max_fsm_pages = 40000
> effective_cache_size = 8000
>
> ********************************************************************

Hmm, how about how many pages are in the various tables, (do a
vacuum verbose <table> for the various tables and what is sort_mem
set to? It's picking the index scan to get the tables in sorted
order, but I wonder if that's really the best plan given it's getting
a large portion of the tables.

Hmm, what does it do if you set enable_indexscan=off; ?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Björn Metzdorf 2003-01-23 15:09:27 Re: tsearch comments
Previous Message Tom Lane 2003-01-23 14:25:53 Re: Fw: configure error with krb5

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2003-01-23 15:26:19 Re: [PERFORM] optimizing query
Previous Message Tom Lane 2003-01-23 14:50:02 Re: Terrible performance on wide selects