"Phoenix Kiula" <phoenix.kiula@xxxxxxxxx> writes: > There are some cases where I would like to bunch queries into a > transaction purely for speed purposes, but they're not interdependent > for integrity. E.g., How do you know you need to do this for speed if you haven't run it yet? I would suggest you build your application around the application needs first, then later look at how to optimize it. Remember the two rules of optimization: 1) Don't 2) (for experts only) Don't yet The only case where you should consider batching together transactions like that is if you're processing a batch data load of some kind. In that case you have a large volume of updates and they're all single-threaded. But usually in that case you want to abort the whole load if you have a problem. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
