From: | Clarence Gardner <clarence(at)silcom(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Sean Leach <sleach(at)netlojix(dot)com> |
Subject: | Lots o' I/O |
Date: | 2003-02-14 22:41:04 |
Message-ID: | Pine.LNX.4.44.0302141400210.21703-100000@liberty.sba2.netlojix.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have a database that was populated about two months ago, and one
particular table has begun causing problems. It's got about 20,000
records, all fixed length of about 1 kbytes. If we do any operation
that involves a sequential scan of that table (e.g., select count(*)),
it now takes about 20 seconds, and according to linux vmstat, reads
275000 disk blocks (275 mbytes). The database is vacuumed each night.
I made a copy of the table (create table c2 select * from c), and a
count on that table takes much less than a second.
Any ideas on what the difference in these tables could be, and how
I can avoid this problem?
Thanks.
From | Date | Subject | |
---|---|---|---|
Next Message | Marc G. Fournier | 2003-02-14 22:55:34 | Re: http://www.pgsql.com/advertising/ many Warning: |
Previous Message | Jeffrey Baker | 2003-02-14 22:38:21 | Re: In 7.3.1, will I be able to reindex toast? |