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

Re: Bug in DROP NOT NULL

From: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Bug in DROP NOT NULL
Date: 2005-04-04 16:18:06
Message-ID: 20050404161806.GC27353@dcc.uchile.cl (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
On Mon, Apr 04, 2005 at 10:17:40PM +0800, Christopher Kings-Lynne wrote:
> >>I don't think that's a bug.  You may not intend ever to cluster on that
> >>index again, and if you try it will tell you about the problem.
> >
> >
> >Except it breaks the 'cluster everything' case:
> >
> >test=# cluster;
> >ERROR:  cannot cluster when index access method does not handle null values
> >HINT:  You may be able to work around this by marking column "a" NOT NULL.
> 
> Any further comments on this?  I still think it's a bug, ie. an 
> invariant that's not being maintained...

I agree with your observation.  What sense does it make to allow marking
an index "clusterable", knowing in advance that it will error out at
cluster time?  None to me.

-- 
Alvaro Herrera (<alvherre[(at)]dcc(dot)uchile(dot)cl>)
"La persona que no querĂ­a pecar / estaba obligada a sentarse
 en duras y empinadas sillas    / desprovistas, por cierto
 de blandos atenuantes"                          (Patricio Vogel)

In response to

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2005-04-04 16:30:50
Subject: Re: [HACKERS] plPHP in core?
Previous:From: Tom LaneDate: 2005-04-04 16:01:41
Subject: Re: [HACKERS] plPHP in core?

pgsql-patches by date

Next:From: Niels BreetDate: 2005-04-04 20:21:41
Subject: tools/entab/halt.c compile fix
Previous:From: Tom LaneDate: 2005-04-04 15:47:06
Subject: Re: DELETE ... USING

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