Skip site navigation (1) Skip section navigation (2)

Re: Testing pg_terminate_backend()

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Testing pg_terminate_backend()
Date: 2008-04-21 08:31:12
Message-ID: 20080421103112.150a821d@mha-laptop (view raw or flat)
Thread:
Lists: pgsql-patches
Bruce Momjian wrote:
> bruce wrote:
> > Magnus Hagander wrote:
> > > Tom Lane wrote:
> > > > Bruce Momjian <bruce(at)momjian(dot)us> 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.

Done that. Also, I needed to replace "gmake" with "make", since I'm on
linux...

Anyway. It's been running for about 12 hours now, and I have *nothing*
in the output file. That tells me that the script doesn't appear to be
working - correct? It should output *something* there, right? (It's
obviously running, because I've got about 400,000 lines in nohup.out..)

Argh. So here I am looking at it now for details, and it seems the
script should be run from src/test/regress, and I ran it from the root
directory.. Oops. Also, I needed to place psql in the path - it failed
to find it, but hid the error message.

Just a hint if someone else is running it ;-)

//Magnus

In response to

Responses

pgsql-patches by date

Next:From: Magnus HaganderDate: 2008-04-21 11:51:10
Subject: Re: libpq Win32 Mutex performance patch
Previous:From: Tom LaneDate: 2008-04-21 05:10:44
Subject: Re: float4/float8/int64 passed by value with tsearch fixup

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group