| From: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
|---|---|
| To: | Xuneng Zhou <xunengzhou(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add tests for object size limits of injection points |
| Date: | 2025-11-12 02:35:26 |
| Message-ID: | 175CC102-DEDF-44BE-AE8E-5A436E7F9173@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Nov 10, 2025, at 18:27, Xuneng Zhou <xunengzhou(at)gmail(dot)com> wrote:
>
> Hi Michael, Chao,
>
> On Mon, Nov 10, 2025 at 11:32 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>>
>> On Mon, Nov 10, 2025 at 10:30:31AM +0800, Chao Li wrote:
>>> Is really confused. The error message says “maximum of 64”, but the
>>> test right uses a name of length 64. I know that the tricky is the
>>> ‘\0’ terminator, but should SQL writer have to keep mind about the
>>> ‘\0’ terminator? Should they just consider maximum length as 63?
>>
>> Right. We could add a "- 1" to the error message printed.
>
> Thanks for the patch. I also agree with Chao's suggestion that the
> error message better reflects the actual character limits. I
> implemented a patch for that and updated the test patch as well.
> Please check.
>
> Best,
> Xuneng
> <v2-0001-injection_points-Report-actual-character-limits-i.patch><v2-0002-injection_points-Add-tests-for-name-limits.patch>
The patch looks good to me.
Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2025-11-12 02:51:51 | Re: Extended Statistics set/restore/clear functions. |
| Previous Message | Thomas Munro | 2025-11-12 02:34:27 | Re: [PATCH] O_CLOEXEC not honored on Windows - handle inheritance chain |