What version of postgres?
8.0.2 ... but I think I've seen this before on 7.3 ...
There are a few possibilities. If you are having a lot of updates to the
table, you can get index bloat. And vacuum doesn't fix indexes. You have
to "REINDEX" to do that. Though REINDEX has the same lock that VACU
Wondering if someone could explain a pecularity for
me:We have a database which takes 1000ms to perform a certain query
on.If I pg_dump that database then create a new database (e.g. "tempdb")
and upload the dump file (thus making a duplicate) then the same query only
takes 190ms !!
Vacuum,
Our dual opteron has been performing well for many
weeks now (after some simple tuning) when all of a sudden the queries have
slowed right down!ie:
DUAL 246 OPTERON:
select count(*) from job_archieve; - Time: 107.24 ms
explain analyse select count(*) from
job_archieve;Aggregate (cost=2
- especially if they automatically
index themselves. I didn't do a vacuum analyse on them so that may explain
why they didn't seem to do much.
Thanks,
Dave
[EMAIL PROTECTED]
- Original Message -
From: "John Arbash Meinel" <[EMAIL PROTECTED]>
To: "SpaceBa
ms
I tried setting up 10-15 indexes yesterday, but couldn't see they were doing
anything. I have since deleted them (on the premise that I didn't have a
clue what I was doing).
I'm not actually running any keys in this database... would that be a
simpler way of running my quer
Hello everyone,First time poster to the
mailing list here.
We have been running pgsql for about a year now at
a pretty basic level (I guess) as a backend for custom
web (intranet) application software. Our database so far is a
"huge" (note sarcasm) 10 Mb containing of about 6 or so princi
