BUG #1274: Trigger sequence incorrect

The following bug has been logged online:

Bug reference:      1274
Logged by:          shancheng

Email address:      sd_shancheng@hotmail.com

PostgreSQL version: 8.0 Beta

Operating system:   Fedora 2

Description:        Trigger sequence incorrect

Details:

The problem happens when I was trying the example that is described in
"PostgreSQL 8.0.0beta1 Documentation, chapt 33.4 --- A Complete Example".

At the last step, as the document says, the result should be:
=> DELETE FROM ttest;
INFO:  trigf (fired before): there are 2 rows in ttest
INFO:  trigf (fired after ): there are 1 rows in ttest
INFO:  trigf (fired before): there are 1 rows in ttest
INFO:  trigf (fired after ): there are 0 rows in ttest
DELETE 2

But what i see is that:
test=# DELETE FROM ttest;
NOTICE:  trigf (fired before): there are 2 tuples in ttest
NOTICE:  trigf (fired before): there are 1 tuples in ttest
NOTICE:  trigf (fired after ): there are 0 tuples in ttest
NOTICE:  trigf (fired after ): there are 0 tuples in ttest
DELETE 2

The execution sequence of the triggers is incorrect.