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

Re: Testing pg_terminate_backend()

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(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-18 21:22:52
Message-ID: 20080418232252.5fb7bc9b@mha-laptop (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
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?


> > 		SLEEP=`expr $RANDOM \* $REGRESSION_DURATION / 32767`
> 
> Uh, where's the randomness coming from?

... but I should probably wait until that one is answered or fixed, I
guess :-)

//Magnus

In response to

Responses

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2008-04-18 21:28:22
Subject: Re: Testing pg_terminate_backend()
Previous:From: Robert TreatDate: 2008-04-18 19:13:03
Subject: Re: get rid of psql welcome message

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2008-04-18 21:28:22
Subject: Re: Testing pg_terminate_backend()
Previous:From: Alvaro HerreraDate: 2008-04-18 20:19:24
Subject: Re: float4/float8/int64 passed by value with tsearchfixup

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