| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Bug in DROP NOT NULL |
| Date: | 2005-04-04 14:17:40 |
| Message-ID: | 42514C84.5030408@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
>> 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...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-04 14:46:41 | Re: BuildFarm status: recent check failures |
| Previous Message | Jim Buttafuoco | 2005-04-04 13:32:45 | Re: BuildFarm status: recent check failures |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-04 15:21:50 | Re: avg(int2) and avg(int8) micro-opt |
| Previous Message | Neil Conway | 2005-04-04 11:19:24 | avg(int2) and avg(int8) micro-opt |