| From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
|---|---|
| To: | Mark Dilger <hornschnorter(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Escape output of pg_amcheck test |
| Date: | 2024-01-08 13:52:26 |
| Message-ID: | D8176FAC-6194-4A15-BD88-C0685FDB6CA1@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Jan 8, 2024, at 5:41 AM, Mark Dilger <hornschnorter(at)gmail(dot)com> wrote:
>
> The /r modifier defeats the purpose of the patch, at least for my perl version, perl 5, version 28, subversion 1 (v5.28.1). With just the /aeg modifier, it works fine.
Nevermind. I might be wrong about that. I didn't have a test case handy that would generate index corruption which would result in characters of the problematic class, and so I quickly wrote some (wrong) instrumentation to try to test your patch.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-01-08 14:01:40 | Re: weird GROUPING SETS and ORDER BY behaviour |
| Previous Message | Mark Dilger | 2024-01-08 13:41:02 | Re: Escape output of pg_amcheck test |