Re: Tighten up a few overly lax regexes in pg_dump's tap tests
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Michael Paquier <michael@paquier.xyz>
Cc: David Rowley <david.rowley@2ndquadrant.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-02-06T09:50:27Z
Lists: pgsql-hackers
Attachments
- pg_dump_testregex.patch (application/octet-stream) patch
> On 6 Feb 2019, at 09:39, Michael Paquier <michael@paquier.xyz> wrote: > And done after checking the whole set. I still think we should enforce one-or-more matching on the OWNER part as well, since matching zero would be a syntax error. There are more .* matches but I’ve only touched the ones which match SQL, since there is a defined grammar to rely on there. The attached patch does that on top of your commit. cheers ./daniel
Commits
-
Align better test output regex with grammar in pg_dump TAP tests
- f339a998ffe6 12.0 landed
-
Tighten some regexes with proper character escaping in pg_dump TAP tests
- d07fb6810e51 12.0 landed