Re: [HACKERS] psql & regress tests

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Ross J(dot) Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu>
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] psql & regress tests
Date: 1999-11-18 23:35:15
Message-ID: 199911182335.SAA18215@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Thu, Nov 18, 1999 at 05:41:36PM -0500, Bruce Momjian wrote:
> > > * Since no one has picked up on my idea to run the tests directly on the
> > > backend, I will keep reiterating this idea until someone shuts me up
> > > :*) The idea would be to have a target "check" in the top level makefile
> > > like this (conceptually):
> >
> > Running the backend standalone does not use locking with other backends,
> > so it is dangerous.
>
> Bruce, how dos this apply to Peter's suggestion? We're talking about
> _regression_ tests. Things to do after changing the code. Do you often
> recompile, and run regression tests against a db with a (now out of date)
> postmaster running against it? Do other developers? I'd have thought a
> complete shutdown/restart is part of the cycle anyway. has to be if an
> initdb is in there of course. Checking to make sure a postmaster isn't
> running could be added to Peter's script, just to be sure.

Regression tests are often run by end-users as part of the install. I
can imagine someone seeing a problem and running the regression tests
while having running backends to see if everything is still working.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 1999-11-18 23:49:51 Re: [HACKERS] psql & regress tests
Previous Message Ross J. Reedstrom 1999-11-18 23:13:33 Re: [HACKERS] psql & regress tests