> Oh, yea, that would be bad. So you want to invalidate the entire > session on any error? That could be done. > > -- > Bruce Momjian | http://candle.pha.pa.us > [EMAIL PROTECTED] | (610) 359-1001
Well, that's exactly the current behaviour, which creates certain problems during interactive or programatic operation. Tom Lane, described an excellent compromise to the problem, using "nested transactions". libpg should be configurable to automatically start a nested transaction for each statement within a transaction allowing the outer transaction to continue in case of error. The error would be communicated to the client in the normal manner. This would not be the default since existing applications rely on the entire transaction aborting. -ESR- ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
