| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, 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-14 02:50:37 |
| Message-ID: | 20170214025037.ehahakimaibtlkpz@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-02-14 11:46:52 +0900, Michael Paquier wrote:
> > I still fail to see why --use-existing as suggested in
> > https://www.postgresql.org/message-id/20170208002900.vkldujzfkwbvqqq7@alap3.anarazel.de
> > isn't sufficient.
>
> Some tests create objects without removing them, meaning that
> continuous runs would fail with only --use-existing. This patch brings
> value in such cases.
You can trivially script the CREATE/DROP DB outside with
--use-existing. Which seems a lot more flexible than adding more and
more options to pg_regress.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-02-14 03:34:35 | Re: Possible TODO: allow arbitrary expressions in event trigger WHEN |
| Previous Message | Michael Paquier | 2017-02-14 02:46:52 | Re: possibility to specify template database for pg_regress |