Re: proposal: separate databases for contrib module testing - Mailing list pgsql-hackers

From Tom Lane
Subject Re: proposal: separate databases for contrib module testing
Date
Msg-id 11439.1354460753@sss.pgh.pa.us
Whole thread Raw
In response to proposal: separate databases for contrib module testing  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: proposal: separate databases for contrib module testing  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> I'd like to change the way we set the CONTRIB_TESTDB name for contrib 
> modules. so that each module doesn't wipe out the previous module's test 
> db.

Personally I always thought that was a feature not a bug.  If we give
each one its own DB, there will be a couple of dozen databases
cluttering the installation at the end of "make installcheck", and no
convenient way to get rid of them.  Moreover, what I think you've got
in mind doesn't work in the "make check" case anyway --- you'd have
little alternative but to test upgrading each one separately.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: [PATCH] Patch to fix a crash of psql
Next
From: Jan Wieck
Date:
Subject: Re: autovacuum truncate exclusive lock round two