| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | SpaceBallOne <space_ball_one(at)hotmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Can anyone explain this: duplicate dbs. |
| Date: | 2005-05-25 03:01:28 |
| Message-ID: | 7665.1116990088@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>> 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, vacuum analyse, and vacuum full analyse does not seem to have an
>> impact on these times.
> Damn, for some reason I didn't read that you had already tried vacuum
> full.
I'm thinking index bloat, and a PG version too old for vacuum full to
recover any index space. But without any information about PG version
or EXPLAIN ANALYZE results, we're all just guessing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-25 03:02:41 | Re: Can anyone explain this: duplicate dbs. |
| Previous Message | Christopher Kings-Lynne | 2005-05-25 03:00:54 | Re: Can anyone explain this: duplicate dbs. |