Re: porting question: funky uid names?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Bixby <mark(at)bixby(dot)org>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: porting question: funky uid names?
Date: 2001-03-10 01:49:36
Message-ID: 12989.984188976@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mark Bixby <mark(at)bixby(dot)org> writes:
> Is it possible to re-run failing regression tests individually?

I believe so, but it's not very convenient in the "runcheck" mode, since
that normally wants to make a fresh install and start a temporary
postmaster. Instead, do a real install, start a real postmaster, and
do "make runtest" to create the regression DB in the real installation.
Then you can basically just do "psql regression <foo.sql" --- look at
the regression driver script to get the details of what switches to
pass and how to do the output comparison.

There are some order dependencies among the tests, but I think all the
ones you were having trouble with should be able to work this way in
an end-state regression DB.

Also, rerunning the whole suite is much quicker this way, since you
don't have to go through install/initdb/start postmaster each time.

BTW, the results you posted looked good --- with the exception of
plpgsql, the failing tests all seemed to be ones that are notorious
for platform-dependent output.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-03-10 02:20:09 Re: AW: AW: AW: WAL does not recover gracefully from ou t-of -dis k-sp ace
Previous Message Mark Bixby 2001-03-10 01:41:14 Re: porting question: funky uid names?