> Josh Berkus wrote:
> Unfortunately, these days only Tom and Neil seem to be
> seriously working on
> the query planner (beg pardon in advance if I've missed
> someone) so I think
> the real answer is that we need another person interested in
> this kind of
> optimization before it's going to get
Hi
I have .5 million rows in a table. My problem is select count(*) takes
ages.
VACUUM FULL does not help. can anyone please tell me
how to i enhance the performance of the setup.
Regds
mallah.
postgresql.conf
--
max_fsm_pages = 55099264 # min max_fsm_rela
Richard Huxton wrote:
On Wednesday 14 April 2004 18:53, Rajesh Kumar Mallah wrote:
Hi
I have .5 million rows in a table. My problem is select count(*) takes
ages. VACUUM FULL does not help. can anyone please tell me
how to i enhance the performance of the setup.
SELECT count(*) from eyp
On Wednesday 14 April 2004 18:53, Rajesh Kumar Mallah wrote:
> Hi
> I have .5 million rows in a table. My problem is select count(*) takes
> ages. VACUUM FULL does not help. can anyone please tell me
> how to i enhance the performance of the setup.
> SELECT count(*) from eyp_rfi;
If this is the a
=?ISO-8859-1?Q?Pailloncy_Jean-G=E9rard?= <[EMAIL PROTECTED]> writes:
> I run the following command three times to prevent cache/disk results.
Do you think that's actually representative of how your database will
behave under load?
If the DB is small enough to be completely cached in RAM, and you
I run the following command three times to prevent cache/disk results.
[...]
dps=> explain analyze SELECT rec_id FROM url WHERE crc32!=0 AND
crc32=764518963 AND status IN (200,304,206) ORDER BY rec_id LIMIT 1;
QUERY PLAN
--
