"Stefan" <sb@drbott.de> writes:
> The problem is that if it is no record in the table, it seems that first the
> INSERT command is issued and after that the UPDATE command is issued, too.
Well, yeah. That's exactly how it's documented to work: an ON INSERT
rule is executed after the INSERT proper.
You could maybe make this work with a BEFORE INSERT trigger.
regards, tom lane