pgsql: injection_points: Add tests for name limits - Mailing list pgsql-committers

From Michael Paquier
Subject pgsql: injection_points: Add tests for name limits
Date
Msg-id E1vIzkP-0069am-1G@gemulon.postgresql.org
Whole thread Raw
List 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@yesql.se>
Reviewed-by: Xuneng Zhou <xunengzhou@gmail.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(-)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Report better object limits in error messages for injection poin
Next
From: Thomas Munro
Date:
Subject: pgsql: Prefer spelling "cacheable" over "cachable".