Bug #839: triggers do not execute in right order in procedures - Mailing list pgsql-bugs

From pgsql-bugs@postgresql.org
Subject Bug #839: triggers do not execute in right order in procedures
Date
Msg-id 20021206070439.B35A0475DD7@postgresql.org
Whole thread Raw
List pgsql-bugs
Eugene Gridasov (eugene@spider.ru) reports a bug with a severity of 1
The lower the number the more severe it is.

Short Description
triggers do not execute in right order in procedures

Long Description
The constraint trigger on delete executes ONLY after procedure
completion, but it does not execute right after delete. WHY?


Sample Code
ex.
table1 has 2 columns: id and name
table2 has 3 columns: id, t1_id(references t1(id) on delete cascade) and 'name' field

i got a procedure (plpgsql)

declare i int;
begin
  select count(*) into i from table2 where t1_id=123;
  raise notice ''rows selected: %'',i;
  delete from table1 where id=123;
  select count(*) into i from table2 where t1_id=123;
  raise notice ''rows selected: %'',i;
end;



No file was uploaded with this report

pgsql-bugs by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Bug #837: Unable to use LATIN9 (=ISO-8859-15) encoding
Next
From: Tom Lane
Date:
Subject: Re: bogus varno EXPLAIN bug (was Re: Explain analyze gives bogus varno for dblink views)