From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | James Coleman <jtc331(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PGXS testing upgrade paths |
Date: | 2020-09-21 15:36:32 |
Message-ID: | 935889.1600702592@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
James Coleman <jtc331(at)gmail(dot)com> writes:
> If there's a better list than this, please let me know, but I figured
> hackers is appropriate since the extension building infrastructure is
> documented in core.
> While working on an in-house extension I realized that while PGXS
> provides the standard regression test infrastructure, I'm not aware of
> an automatic or standard way to test all upgrade paths provided by the
> extension.
The recommended way to deal with updates these days is to leave the
original extension script as-is and just write update scripts
(1.0--1.1, 1.1--1.2, etc). That way, application of the updates
is tested automatically every time you do CREATE EXTENSION.
Now, if you also want to check that the intermediate states still
behave as intended, I don't see much of a solution that doesn't
involve custom test scaffolding.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | James Coleman | 2020-09-21 15:42:18 | Re: PGXS testing upgrade paths |
Previous Message | Tom Lane | 2020-09-21 15:09:23 | Re: Lift line-length limit for pg_service.conf |