proposal: separate databases for contrib module testing

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: proposal: separate databases for contrib module testing
Date: 2012-12-02 04:33:25
Message-ID: 50BADA15.6000004@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. The reason is that this will let us test upgrading them using
pg_upgrade much more easily. Not testing this is a significant hole in
the pg_upgrade testing regime.

This can be achieved by a fairly simple change in Makefile.global.in
along these lines:

ifneq ($(MODULE_big),)
CONTRIB_TESTDB = contrib_regression_$(MODULE_big)
else
ifneq ($(MODULES),)
CONTRIB_TESTDB = contrib_regression_$(MODULES)
else
CONTRIB_TESTDB = contrib_regression
endif
endif

plus some changes in the dblink tests / results that rely on the
database name.

The downside is that this involves in increase in space of 6.5Mb to
7.5Mb per module. That doesn't seem huge in these days when a standard
commodity hard drive is 500Gb and up.

Thoughts?

cheers

andrew

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit kapila 2012-12-02 05:19:34 Re: Proposal for Allow postgresql.conf values to be changed via SQL
Previous Message Noah Misch 2012-12-02 02:07:36 Re: ALTER TABLE ... NOREWRITE option