Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
| От | Noah Misch |
|---|---|
| Тема | Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set |
| Дата | |
| Msg-id | 20220511053255.GA2578591@rfd.leadboat.com обсуждение |
| Ответ на | Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: Rewriting the test of pg_upgrade as a TAP test - take three - remastered set
|
| Список | 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?
В списке pgsql-hackers по дате отправления: