pgsql: injection_points: Add tests for name limits

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: injection_points: Add tests for name limits
Date: 2025-11-12 01:34:09
Message-ID: E1vIzkP-0069am-1G@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

injection_points: Add tests for name limits

The maximum limits for point name, library name, function name and
private area size were not kept track of in the tests. The new function
introduced in 16a2f706951e gives a way to trigger them. This is not
critical but cheap to cover.

While on it, this commit cleans up some of the tests introduced by
16a2f706951e for NULL inputs by using more consistent argument values.
The coverage does not change, but it makes the whole less confusing with
argument values that are correct based their position in the SQL
function called.

Reviewed-by: Daniel Gustafsson <daniel(at)yesql(dot)se>
Reviewed-by: Xuneng Zhou <xunengzhou(at)gmail(dot)com>
Discussion: https://postgr.es/m/aRE7zhu6wOA29gFf@paquier.xyz

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/fb9bff04542138d7217e79fc5e1bb9d5fabd9026

Modified Files
--------------
.../injection_points/expected/injection_points.out | 21 +++++++++++++++++----
.../injection_points/sql/injection_points.sql | 17 +++++++++++++----
2 files changed, 30 insertions(+), 8 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2025-11-12 01:35:39 pgsql: Prefer spelling "cacheable" over "cachable".
Previous Message Michael Paquier 2025-11-12 01:20:01 pgsql: Report better object limits in error messages for injection poin