From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Blasby <dblasby(at)refractions(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SELECT * FROM <table> LIMIT 1; is really slow |
Date: | 2004-05-27 02:21:19 |
Message-ID: | 5660.1085624479@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Blasby <dblasby(at)refractions(dot)net> writes:
> I have another copy of this table in another database - vacuum analyse
> verbose says its "only" 1,500,000 pages (vs 2,800,000).
Hmm ... this is consistent with the idea that you did an UPDATE
affecting every row of the table. That would generate N new rows which
would all get added to the end of the table, if there were no dead space
available within the table. After commit you have a lot of pages worth
of dead tuples followed by a lot of pages worth of live tuples. Plain
VACUUM cannot do much to fix this since it doesn't move rows around.
VACUUM FULL will fix it, but its index-update overhead is high enough
that CLUSTER is a better deal.
See followup message discussing ALTER TABLE as another alternative.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | James Robinson | 2004-05-27 03:43:19 | Re: tablespaces and DB administration |
Previous Message | Tom Lane | 2004-05-27 02:06:13 | Re: SELECT * FROM <table> LIMIT 1; is really slow |