| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Improving the notation for ecpg.addons rules |
| Date: | 2024-08-20 18:33:23 |
| Message-ID: | 1625779.1724178803@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
>> It looks like %replace_line expects all its elements to have one space
>> between each token, still this is not enforced with a check across its
>> hardcoded elements?
> Yeah, I was wondering about that. I wouldn't do it exactly like
> that, but with a check that the entry gets matched somewhere.
Here's a patch for that (again based on the other patch series).
This did not turn up anything interesting, but it's probably
worth keeping.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| check-usage-of-parse.pl-hash-tables.patch | text/x-diff | 3.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2024-08-20 18:37:34 | Re: MultiXact\SLRU buffers configuration |
| Previous Message | David G. Johnston | 2024-08-20 17:55:46 | Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs |