Re: Tighten up a few overly lax regexes in pg_dump's tap tests
David Rowley <david.rowley@2ndquadrant.com>
From: David Rowley <david.rowley@2ndquadrant.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Daniel Gustafsson <daniel@yesql.se>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-02-05T04:46:55Z
Lists: pgsql-hackers
Attachments
- tighten_up_pg_dump_tap_tests_v2.patch (application/octet-stream) patch v2
On Tue, 5 Feb 2019 at 14:41, Michael Paquier <michael@paquier.xyz> wrote: > Instead of the approach you are > proposing, perhaps it would make sense to extend this way of doing > things then? For example some tests with CREATE CONVERSION do so. It > looks much more portable than having to escape every dot. I'm not particularly excited either way, but here's a patch with it that way. I did leave a couple untouched as there was quite a bit of escaping going on already. I didn't think switching between \Q and \E would have made those ones any more pleasing to the eye. -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
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