| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Rewriting the test of pg_upgrade as a TAP test |
| Date: | 2017-09-19 22:57:26 |
| Message-ID: | bc051ac1-f326-89e2-8762-5303d32e6f71@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/19/17 07:37, Michael Paquier wrote:
>>> This patch is logged as "waiting on author" in the current commit
>>> fest, but any new patch will depend on the feedback that any other
>>> hacker has to offer based on the set of ideas I have posted upthread.
>>> Hence I am yet unsure what is the correct way to move things forward.
>>> So, any opinions? Peter or others?
>>
>> I think the first step is to send the rebased version of the patch. It
>> was last posted in April ...
>
> Here you go. I have not done anything fancy for cross-version tests yet.
To get things rolling, I have committed just the basic TAP tests, to
give it a spin on the build farm. I'll work through the rest in the
coming days.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-09-19 23:00:25 | Re: Rewriting the test of pg_upgrade as a TAP test |
| Previous Message | Peter Eisentraut | 2017-09-19 22:56:14 | pgsql: Add basic TAP test setup for pg_upgrade |