Re: DROP CONSTRAINT (UNIQUE) preliminary support

> > > Since then, I decided to complete the ADD CONSTRAINT stuff first.  I've
> > > _almost_ finished ADD UNIQUE and ADD PRIMARY.  I'll probably
> > submit a patch
> > > for those in the next couple of days.  After that I'll worry about DROP
> > > CONSTRAINT again.
> >
> > Oh, fine.  Just checking.  Didn't want you to think we weren't
> > interested in your work.
>
> Well - it isn't as sexy as UNDO/REDO support, planner optimisation or an
> overwriting storage manager, but there's nothing more annoying to me as a
> web developer to have inflexible schema.  How much do I want that DROP
> COLUMN feature!  It's simply not feasible to recreate the table without the
> column on a live server.

Agreed.  We need to bite the bullet, decide on a plan, and get going.
My vote is to make a second copy of the table then update pg_class.  Now
that we have files as numbers, relfilenode, we can do that reliably.
Let's get started!

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026