bruce wrote: > bruce wrote: > > Magnus Hagander wrote: > > > Tom Lane wrote: > > > > Bruce Momjian <[EMAIL PROTECTED]> writes: > > > > > Attached is my test script. I ran it for 14 hours (asserts on), > > > > > running 450 regression tests, with up to seven backends killed per > > > > > regression test. > > > > > > > > Hmm, there are something on the order of 10000 SQL commands in our > > > > regression tests, so even assuming perfect randomness you've exercised > > > > SIGTERM on maybe 10% of them --- and of course there's multiple places > > > > in a complex DDL command where SIGTERM might conceivably be a problem. > > > > > > > > Who was volunteering to run this 24x7 for awhile? > > > > > > That was me. As long as the script runs properly on linux, I can get > > > that started as soon as I'm fed instructions on how to do it :-) Do I > > > just fix the paths and set it running, or do I need to prepare > > > something else? > > > > Nothing special to prepare. Compile with asserts enabled, and run the > > script. The comment at the top explains how to analyze the log for > > interesting error messages. > > Oh, you need to set a variable in the script indicating the average > number of seconds it takes to run the regression test on your system.
And you have to set the location of the output file and where your regression test directory is located. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-patches mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches