Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Bug in DROP NOT NULL
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
- Cc: Hackers <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: Bug in DROP NOT NULL
- Date: Thu, 31 Mar 2005 09:59:55 -0500
- Message-id: <5419.1112281195@sss.pgh.pa.us> <text/plain>
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes: >> You can drop a NOT NULL on a column, even if that column is part of an >> index that is clustered, where the index does not index NULLs. 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. regards, tom lane
- References:
- Bug in DROP NOT NULL
- From: Christopher Kings-Lynne
- Re: Bug in DROP NOT NULL
- From: Christopher Kings-Lynne
- Bug in DROP NOT NULL
- Prev by Date: Re: Understanding pg_xlog
- Next by Date: Re: TSearch2 performance issue?
- Previous by thread: Re: Bug in DROP NOT NULL
- Next by thread: Re: [COMMITTERS] pgsql: Translation updates
- Indexes: