Re: Tighten up a few overly lax regexes in pg_dump's tap tests
| От | David Rowley |
|---|---|
| Тема | Re: Tighten up a few overly lax regexes in pg_dump's tap tests |
| Дата | |
| Msg-id | CAKJS1f8pr-8DF2o4njv9oMEH0M1Ta_2kEE2eet8gFjmsMOBFug@mail.gmail.com обсуждение |
| Ответ на | Re: Tighten up a few overly lax regexes in pg_dump's tap tests (Daniel Gustafsson <daniel@yesql.se>) |
| Ответы |
Re: Tighten up a few overly lax regexes in pg_dump's tap tests
|
| Список | pgsql-hackers |
On Tue, 5 Feb 2019 at 01:12, Daniel Gustafsson <daniel@yesql.se> wrote: > We may also want to use the + metacharacter instead of * in a few places, since > the intent is to always match something, where matching nothing should be > considered an error: > > - qr/^ALTER TEXT SEARCH DICTIONARY dump_test.alt_ts_dict1 OWNER TO .*;/m, > + qr/^ALTER TEXT SEARCH DICTIONARY dump_test\.alt_ts_dict1 OWNER TO .*;/m, I looked for instances of * alone and didn't see any. I only saw ones prefixed with ".", in which case, isn't that matching 1 or more chars already? -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: