Skip site navigation (1) Skip section navigation (2)

Re: CLUSTER loses nulls (was Re: [ADMIN] Still a bug in the VACUUM)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CLUSTER loses nulls (was Re: [ADMIN] Still a bug in the VACUUM)
Date: 2003-03-03 03:42:27
Message-ID: 28468.1046662947@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>> * Make CLUSTER error out if the target index is not of an 'amindexnulls'
>> index AM.  This would amount to restricting CLUSTER to b-trees, which is
>> annoying.

> I think this solution is fine - we just need to fix GiST to index nulls
> one day :)

Yeah, I think this is the appropriate stopgap for 7.3.* in any case.
If someone wants to improve it later, fine...

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-03-03 03:45:07
Subject: Re: CLUSTER loses nulls (was Re: [ADMIN] Still a bug in the VACUUM)
Previous:From: Rod TaylorDate: 2003-03-03 03:37:25
Subject: Re: CLUSTER loses nulls (was Re: [ADMIN] Still a bug in the VACUUM)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group