| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set |
| Date: | 2022-05-11 05:32:55 |
| Message-ID: | 20220511053255.GA2578591@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 11, 2022 at 10:29:44AM +0900, Michael Paquier wrote:
> On Mon, May 09, 2022 at 12:18:39PM +0900, Michael Paquier wrote:
> > All these fixes lead me to the attached patch.
>
> I have applied this stuff as of 7dd3ee5, in time for beta1, and closed
> the open item. One difference is that I've added one backslash
> surrounding the double quote at the beginning *and* the end of the
> database name in the patch. However, the original case was different,
> with:
> - At the beginning of the database name, one backslash before and
> after the double quote.
> - At the end of the database name, two backslaces before the double
> quote and three after the double quote.
Why did you discontinue testing the longstanding test database name?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-05-11 05:34:25 | Re: Estimating HugePages Requirements? |
| Previous Message | Thomas Munro | 2022-05-11 05:28:15 | Re: Unstable tests for recovery conflict handling |