Re: Drop constraint in PostgreSQL 7.1.2

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Vilson farias <vilson(dot)farias(at)digitro(dot)com(dot)br>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Drop constraint in PostgreSQL 7.1.2
Date: 2003-02-04 19:42:27
Message-ID: 20030204114030.S7488-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 4 Feb 2003, Vilson farias wrote:

>
> Ok, but I'm having some problems to identify wich triggers should be
> destroyed. How can I remove those triggers? Can I just delete these records
> from pg_trigger?

>
> ALTER TABLE cham_atendimento
> ADD CONSTRAINT RLoginXAtend FOREIGN KEY (pa, dt_login)
> REFERENCES pa__login;
>
> bxs=# select * from pg_trigger where tgconstrname = 'rloginxatend';

- These three constraints are the ones you need

> bxs=# drop trigger RI_ConstraintTrigger_20885 on cham_atendimento;
> ERROR: DropTrigger: there is no trigger ri_constrainttrigger_20885 on
> relation cham_atendimento
> bxs=# drop trigger RI_ConstraintTrigger_20885 on pa__login;
> ERROR: DropTrigger: there is no trigger ri_constrainttrigger_20885 on
> relation pa__login
>
> How can I remove those triggers? Can I just delete these records from

You'll need to double quote the names because they're mixed case.

> pg_trigger?

Not without also altering reltriggers on pg_class.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ian Harding 2003-02-04 19:45:49 Rules with "Where" Referencing Other Tables
Previous Message Gregory Stark 2003-02-04 19:27:34 now() more precise than the transaction