From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | joepie Platteau <joepie(dot)Platteau(at)kulak(dot)ac(dot)be> |
Cc: | PgSQL Novice ML <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Database Performance problem |
Date: | 2003-01-20 15:33:30 |
Message-ID: | 3172.1043076810@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-novice |
joepie Platteau <joepie(dot)Platteau(at)kulak(dot)ac(dot)be> writes:
> shared_buffers = 128
Try boosting that to 1000 or so. The default sort_mem is on the miserly
side as well; you could try 5000 or 10000 for that.
But probably a more important bit of advice is to run ANALYZE. I think
most likely Postgres is choosing a bad query plan because it doesn't
have any statistics about the table contents.
If ANALYZE doesn't help, let's see the output of EXPLAIN ANALYZE for the
problem query.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-20 15:38:25 | Re: intervals in 7.3.1 |
Previous Message | Chris Boget | 2003-01-20 15:28:50 | Re: Altering a table - positioning new columns |
From | Date | Subject | |
---|---|---|---|
Next Message | Manfred Koizar | 2003-01-20 15:34:22 | Re: UNION? |
Previous Message | Conxita Marín | 2003-01-20 14:55:57 | Re: quoted_literal with numeric variable |