Re: Improving the notation for ecpg.addons rules
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2024-08-23T02:03:37Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes: > The patch does not apply on HEAD due to the dependency with the other > things you are proposing, and I would have hardcoded failures to check > that the reports are correct, but that looks neat on read. I did test it by injecting errors, but I don't see why we'd leave those in place? Anyway, my thought was to merge this into the other patch series, but I didn't do that yet. regards, tom lane
Commits
-
ecpg: invent a saner syntax for ecpg.addons entries.
- dbedc461b4e7 18.0 landed
-
ecpg: add cross-checks to parse.pl for usage of internal tables.
- d2f41b4621de 18.0 landed