[BUGS] Sequence bug in insert trigger

Sequence bug in insert trigger ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Sequence bug in insert trigger Long Description Insert triggers always read sequences at their min (or start) value. This only occurs when trigger

[BUGS] Sending result sets from backend to frontend is _slow_

Glen Parker ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Sending result sets from backend to frontend is _slow_ Long Description When operating over a fast network (ethernet), the sending of select result rows from the back

Re: [BUGS] Sending result sets from backend to frontend is _slow_

[EMAIL PROTECTED] writes: > When operating over a fast network (ethernet), the sending of select > result rows from the backend is very slow, ie. it uses only a small > fraction of available network bandwidth. I am running postgres 7.0.2 > on a Redhat 6.1 install on x86, and using the postodbc dr

Re: [BUGS] Sequence bug in insert trigger

[EMAIL PROTECTED] writes: > insert into test_table values('jim'); > --Doh! rowver = 1 (should be 2) 1 is correct for the first nextval() from a sequence. > insert into test_table values('joe'); > --Doh! rowver = 1 (should be 3) I can't duplicate this under either 7.0.2 or curren