The following bug has been logged on the website:
Bug reference: 7643
Logged by: Haribabu
Email address: haribabu.ko...@huawei.com
PostgreSQL version: 9.2.1
Operating system: Suse Linux 10.2
Description:
Problem Reproduction:
1. Add recovery.conf to the database direc
Tom,
There is also a minor bug when trying to do same thing with RULE (it
doesn't produce an error but the notice is not correct when function is
called for the second time):
CREATE OR REPLACE FUNCTION drop_rule_test() RETURNS void AS $$
BEGIN
DROP RULE IF EXISTS invalid_rule ON test1;
END;
ser...@booksys.com writes:
> CREATE OR REPLACE FUNCTION drop_trigger_test() RETURNS void AS $$
> BEGIN
>DROP TRIGGER IF EXISTS invalid_trigger ON test1;
> END; $$ LANGUAGE plpgsql;
> 4. SELECT drop_trigger_test();
> Result:
> NOTICE: trigger "invalid_trigger" for table "test1" does not exist,
