RE: DROP CONSTRAINT patch - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject RE: DROP CONSTRAINT patch
Date
Msg-id ECEHIKNFIMMECLEBJFIGKEJNCAAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to DROP CONSTRAINT patch  (Christopher <chriskl@familyhealth.com.au>)
Responses Re: DROP CONSTRAINT patch  (Bruce Momjian <pgman@candle.pha.pa.us>)
RE: DROP CONSTRAINT patch  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-hackers
Anyone looked at this yet?

Also, if someone could tell me where I should attempt to add a regression
test and what, exactly, I should be regression testing it would be
helpful...

Chris

> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Christopher
> Sent: Sunday, 20 May 2001 3:50 PM
> To: pgsql-hackers@postgresql.org
> Subject: [HACKERS] DROP CONSTRAINT patch
>
>
> Hi all,
>
> Attached is my patch that adds DROP CONSTRAINT support to PostgreSQL.  I
> basically want your guys feedback.  I have sprinkled some of my q's thru
> the text delimited with the @@ symbol.  It seems to work perfectly.
>
> At the moment it does CHECK constraints only, with inheritance.  However,
> due to the problem mentioned before with the mismatching between inherited
> constraints it may be wise to disable the inheritance feature for a while.
> it is written in an extensible fashion to support future dropping of other
> types of constraint, and is well documented.
>
> Please send me your comments, check my use of locking, updating of
> indices, use of ERROR and NOTICE, etc. and I will rework the patch based
> on feedback until everyone
> is happy with it...
>
> Chris
>



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: RE: Plans for solving the VACUUM problem
Next
From: Zeugswetter Andreas SB
Date:
Subject: AW: Is stats update during COPY IN really a good idea?