Re: [PATCH] Using named captures in Catalog::ParseHeader()
От | Dagfinn Ilmari Mannsåker |
---|---|
Тема | Re: [PATCH] Using named captures in Catalog::ParseHeader() |
Дата | |
Msg-id | 875y7qs85s.fsf@wibble.ilmari.org обсуждение исходный текст |
Ответ на | Re: [PATCH] Using named captures in Catalog::ParseHeader() (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: [PATCH] Using named captures in Catalog::ParseHeader()
|
Список | 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
В списке pgsql-hackers по дате отправления: