RE: DROP CONSTRAINT patch

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: DROP CONSTRAINT patch
Date: 2001-05-22 06:25:40
Message-ID: ECEHIKNFIMMECLEBJFIGKEJNCAAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org]On Behalf Of Christopher
> Sent: Sunday, 20 May 2001 3:50 PM
> To: pgsql-hackers(at)postgresql(dot)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
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2001-05-22 07:19:53 AW: Is stats update during COPY IN really a good idea?
Previous Message Bruce Momjian 2001-05-22 04:38:15 Re: RE: Plans for solving the VACUUM problem