From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Kishore B <kishorebh(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Need help in setting optimal configuration for a huge database. |
Date: | 2005-10-22 22:15:43 |
Message-ID: | 3994.1130019343@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
Kishore B <kishorebh(at)gmail(dot)com> writes:
> Even a basic query like select count(*) from bigger_table is
> taking about 4 minutes to return.
You do realize that "select count(*)" requires a full table scan in
Postgres? It's never going to be fast.
If that's not where your performance problem really is, you need to
show us some of the actual problem queries. If it is, you should
rethink why your application needs an exact row count.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kishore B | 2005-10-23 02:05:50 | Re: Need help in setting optimal configuration for a huge database. |
Previous Message | Kirby Ubben | 2005-10-22 22:04:19 | Pgpool errors: pgpool 2.6.4 postgres 7.3.10 ProcessFrontendResponse: failed to read kind from frontend. fronend abnormally exited |
From | Date | Subject | |
---|---|---|---|
Next Message | Kishore B | 2005-10-23 02:05:50 | Re: Need help in setting optimal configuration for a huge database. |
Previous Message | Karl O. Pinc | 2005-10-22 22:03:03 | Re: Need help in setting optimal configuration for a huge |