"Ed L." <[EMAIL PROTECTED]> writes:
> Are triggers on sequences a reasonable feature request/hope for Pgsql?
I don't think so. Since sequences are inherently not transactional,
it seems wrong to fire a transactional behavior as a side effect of
nextval(). What exactly are you expecting the trigger to do, and
how is it going to do it in a way that won't get rolled back if the
calling transaction fails later?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
