Re: [PATCH] Using named captures in Catalog::ParseHeader()
Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
From: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
To: Michael Paquier <michael@paquier.xyz>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Peter Eisentraut
<peter@eisentraut.org>
Date: 2023-06-14T09:30:23Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes: > On Thu, Jun 01, 2023 at 01:12:22PM +0100, Dagfinn Ilmari Mannsåker wrote: >> While I was rewriting the regexes I noticed that they were inconsistent >> about whether they accepted whitespace in the parameter lists, so I took >> the liberty to make them consistently allow whitespace after the opening >> paren and the commas, which is what most of them already did. > > That's the business with \s* in CATALOG. Is that right? Indeed, > that's more consistent. Yes, \s* means "zero or more whitespace characters". >> I've verified that the generated postgres.bki is identical to before, >> and all tests pass. > > I find that pretty cool. Nice. Patch looks OK from here. Thanks for the review! - ilmari
Commits
-
Use named captures in Catalog::ParseHeader()
- 23d8624fe52e 17.0 landed