> > Using two transactions, one for the vital components, the other for > > non-vital portions. > > > > Or do we need to revisit how these tables are updated? > > Yes, it would be possible to commit the filename/path inserts > immediately (i.e. 1 insert per transaction) but still do the > file inserts within a larger transaction.
Not really, if you want/need to refer to them from transaction 1. If you add them in transaction2, transaciton 1 will *never* see those rows. It'll hav eto commit and open transactio 3 before they become visible. > I'm not sure if > postgresql would need two connections to do this or if it can > handle multiple simultaneous transactions on one connection. It would require multiple connections. Only one transaction at a time can live in a single connection. //Magnus ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
