Re: proposal: separate databases for contrib module testing

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: separate databases for contrib module testing
Date: 2012-12-02 15:05:53
Message-ID: 11439.1354460753@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2012-12-02 15:13:18 Re: autovacuum truncate exclusive lock round two
Previous Message Tatsuo Ishii 2012-12-02 13:25:35 Re: [PATCH] Patch to fix a crash of psql