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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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)
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-04-04 16:30:50 | Re: [HACKERS] plPHP in core? |
Previous Message | Tom Lane | 2005-04-04 16:01:41 | Re: [HACKERS] plPHP in core? |
From | Date | Subject | |
---|---|---|---|
Next Message | Niels Breet | 2005-04-04 20:21:41 | tools/entab/halt.c compile fix |
Previous Message | Tom Lane | 2005-04-04 15:47:06 | Re: DELETE ... USING |