Re: possibility to specify template database for pg_regress

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: possibility to specify template database for pg_regress
Date: 2017-02-08 07:24:08
Message-ID: CAFj8pRAzg6=9tf9hUbO2UaKug6vYfa9-PnQneVNHcjf2jJM1Ow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2017-02-08 1:30 GMT+01:00 Michael Paquier <michael(dot)paquier(at)gmail(dot)com>:

> On Wed, Feb 8, 2017 at 9:23 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > I ran into a use-case just today: I wanted to run one particular
> > regression test script under CLOBBER_CACHE_ALWAYS, but it needed
> > stuff created by earlier scripts, and I didn't especially want to
> > run all of those scripts under CCA. With a way to select a template,
> > I could've run the earlier scripts in a normal build, renamed the
> > ending-state regression database to something else, and then installed
> > a CCA-enabled executable and run a test with just the script of
> > interest. The way I actually got it done was considerably hackier :-(
>
> Looking at the code, --dbname can actually accept a list of databases.
> Perhaps we could just have the equivalent for templates? I think that
> we just need to be sure that the template list matches the length of
> the database list if the template list is longer than one.
>

What is sense for list of databases?

Some option --template can be great - with backpatch if it is possible.

Regards

Pavel

> --
> Michael
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-02-08 07:30:26 Re: possibility to specify template database for pg_regress
Previous Message Dilip Kumar 2017-02-08 06:59:25 Re: Parallel bitmap heap scan