Quick Links

Re: SELECT * FROM <table> LIMIT 1; is really slow

From:	Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To:	Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc:	David Blasby <dblasby(at)refractions(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject:	Re: SELECT * FROM <table> LIMIT 1; is really slow
Date:	2004-05-27 01:36:33
Message-ID:	40B54621.1070001@familyhealth.com.au
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

> It wouldn't; you'd need vacuum full to collapse out the dead space.
> You could also try CLUSTER which is faster than VACUUM FULL when most
> of the data has to be moved anyway. (Some days I think we should dump
> VACUUM FULL, because it's optimized for a case that's no longer very
> interesting...)

Out of interest, is CLUSTER another fast way of truly removing OIDs from
a table, after going SET WITHOUT OIDS?

Chris

In response to

Re: SELECT * FROM <table> LIMIT 1; is really slow at 2004-05-26 22:17:55 from Tom Lane

Responses

Re: SELECT * FROM <table> LIMIT 1; is really slow at 2004-05-27 02:06:13 from Tom Lane

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Christopher Kings-Lynne	2004-05-27 01:40:29	Re: tablespaces and DB administration
Previous Message	Stephan Szabo	2004-05-26 23:35:52	Re: Nested xacts: looking for testers and review