At 11:49 AM 4/26/02 -0400, Tom Lane wrote: >I'm still looking for an example of something that is (a) reasonable >to set on a per-backend basis, and (b) not reasonable to roll back >if it's set in a transaction that fails.
The way I see it is if (a) and you don't want it rolled back, you could put it in a transaction of its own. BEGIN; SET backend pref; COMMIT; And if that transaction fails, maybe it should :). So other than for performance, the example should also have a reason to belong with other statements in a transaction. Have a nice weekend, Link. ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
