[EMAIL PROTECTED] writes:
> INSERT INTO test2
> SELECT 1,1 UNION
> SELECT 1,1;
> field1|field2
> ------+------
> 1| 2
> (this output is wrong as field2 should be 3 after the second and third
> insert)
"Second and third insert"? SELECT 1,1 UNION SELECT 1,1 produces only
a single tuple, since UNION is defined to eliminate duplicates. So
your example appears to be correct as given.
However, if I try it with UNION ALL (which doesn't eliminate duplicates)
then I still get the same behavior; that does seem to be a bug.
I confirm your second bug report about ON DELETE rules, too.
I'm using current sources, so this hasn't been fixed since 6.5 :-(.
This looks like Jan Wieck's turf --- Jan, are you listening?
regards, tom lane
