Re: Tighten up a few overly lax regexes in pg_dump's tap tests - Mailing list pgsql-hackers

From David Rowley
Subject Re: Tighten up a few overly lax regexes in pg_dump's tap tests
Date
Msg-id CAKJS1f8pr-8DF2o4njv9oMEH0M1Ta_2kEE2eet8gFjmsMOBFug@mail.gmail.com
Whole thread Raw
In response to Re: Tighten up a few overly lax regexes in pg_dump's tap tests  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Tighten up a few overly lax regexes in pg_dump's tap tests  ("David G. Johnston" <david.g.johnston@gmail.com>)
List 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 by date:

Previous
From: David Rowley
Date:
Subject: Re: Tighten up a few overly lax regexes in pg_dump's tap tests
Next
From: "David G. Johnston"
Date:
Subject: Re: Tighten up a few overly lax regexes in pg_dump's tap tests