From: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
---|---|
To: | pghackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | [HACKERS] Trigger drop/create bug? |
Date: | 2000-01-28 19:31:21 |
Message-ID: | 3891EE89.F9EF18DB@austin.rr.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The following drop fails due to non-existent trigger, but then the
subsequent create fails due to existing trigger. What's happening?
Is this a known problem?
Pg 6.5.2, RH6.1, 2.2.12-20smp, Pentium III i686
(from my postgres server log...)
20000128.13:21:05.881 [2810] query: DROP TRIGGER
ems_user_insert_trigger ON employee;
20000128.13:21:05.881 [2810] ProcessUtility: DROP TRIGGER
ems_user_insert_trigger ON employee;
20000128.13:21:05.881 [2810] ERROR: DropTrigger: there is no trigger
ems_user_insert_trigger on relation employee
20000128.13:21:05.882 [2810] query: CREATE TRIGGER
ems_user_insert_trigger AFTER INSERT ON ems_user FOR EACH ROW EXECUTE
PROCEDURE add_bad_passwd_rec();
20000128.13:21:05.882 [2810] ProcessUtility: CREATE TRIGGER
ems_user_insert_trigger AFTER INSERT ON ems_user FOR EACH ROW EXECUTE
PROCEDURE add_bad_passwd_rec();
20000128.13:21:05.883 [2810] ERROR: CreateTrigger: trigger
ems_user_insert_trigger already defined on relation ems_user
Cheers,
Ed Loehr
From | Date | Subject | |
---|---|---|---|
Next Message | Ed Loehr | 2000-01-28 19:33:40 | Re: [HACKERS] Trigger drop/create bug? |
Previous Message | Hannu Krosing | 2000-01-28 19:03:34 | Re: [HACKERS] OO and tuples of different types |