On Fri, Feb 10, 2006 at 07:22:10AM -0800, Karl Hakimian wrote: > On Fri, Feb 10, 2006 at 10:12:10AM -0500, Dan Langille wrote: > > If you have concurrent jobs, what happens when job #1 wants to add a > > file to the table, and job #2 wants to add the same file? How do you > > ensure that both transactions work without failure? > > That looks like the biggest possible problem, but if you don't supply > the field, postgres will set it to the default which will be correctly > setting it from the sequence.
Re-reading, I think I misunderstood your question. I don't see how two jobs can be adding the same file, the same path/filename yes, but not the same file. My earlier suggestion was to leave the path/filename adding the same -- Karl Hakimian [EMAIL PROTECTED] ------------------------------------------------------- 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&kid=103432&bid=230486&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
