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

Re: "make check" improvement for cygwin

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: "PG Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: "make check" improvement for cygwin
Date: 2003-10-29 00:32:56
Message-ID: 003a01c39db4$346b57b0$6401a8c0@DUNSLANE (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
----- Original Message ----- 
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: "PG Patches" <pgsql-patches(at)postgresql(dot)org>
Sent: Monday, October 27, 2003 11:12 PM
Subject: Re: [PATCHES] "make check" improvement for cygwin

> "Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
> > Something like this?
> >     make MAX_CONNECTIONS=10 check
> > Maybe in the case of cygwin, where it is almost bound to fail without
> > restrictions, we could put out a warning if it isn't used.
> That works for me.  Possibly you should pop this proposal up on
> pghackers, to make sure other people buy into it before you go to
> the trouble of coding it...

Well, I posted the note last night but I finished the patch today, because
it was very simple and took so little time.

I think this does what you suggested.

If it's accepted I'll do a doc patch to match.



Attachment: pg_regress.patch
Description: application/octet-stream (3.9 KB)

In response to


pgsql-patches by date

Next:From: Jason TishlerDate: 2003-10-29 13:40:35
Subject: Re: "make check" improvement for cygwin
Previous:From: Tom LaneDate: 2003-10-28 20:29:23
Subject: Re: Ant version detection

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