Re: [PATCH] Little refactoring of portalcmds.c - Mailing list pgsql-hackers

From Zizhuan Liu
Subject Re: [PATCH] Little refactoring of portalcmds.c
Date
Msg-id 177976696610.313758.9369660411072671375.pgcf@coridan.postgresql.org
Whole thread
In response to Re: [PATCH] Little refactoring of portalcmds.c  (Zizhuan Liu <44973863@qq.com>)
List pgsql-hackers
The following review has been posted through the commitfest application:
make installcheck-world:  not tested
Implements feature:       not tested
Spec compliant:           not tested
Documentation:            not tested

The newly introduced check_cursor_name() implements the logic to reject empty cursor names, which matches the existing
checksin PerformCursorOpen() and PerformPortalFetch().
 

However, this helper function is not a good fit for PerformPortalClose(). At the start of this function, there is a
checkfor name == NULL — a NULL name corresponds to the CLOSE ALL command — and this check runs prior to validating
whetherthe name is an empty string.
 

While calling check_cursor_name() inside PerformPortalClose() would keep the current behavior intact, it could confuse
futurereaders. This approach also fails to achieve truly consistent cursor name validation across all three functions,
andmay add extra maintenance burdens in the long term.
 

On the other hand, if we only refactor PerformCursorOpen() and PerformPortalFetch(), the change would end up being
ratherminimal.
 

Considering all these factors, I'd suggest leaving the code as it is and skipping this refactoring.

pgsql-hackers by date:

Previous
From: Zizhuan Liu
Date:
Subject: Re: [PATCH] Little refactoring of portalcmds.c
Next
From: Chao Li
Date:
Subject: Fix bug of CHECK constraint enforceability recursion