Jan 2024

2 commits
Clean up some edge cases in plpgsql's %TYPE parsing.
5 Jan 2024Tom Lanemaster17beta1REL_19_STABLE17beta1REL_18_STABLE17beta1REL_17_STABLE17beta1
LLM analysis, 100% suremodified before commitmoderate changesfrom patchset #150 of 1 reviewer saw the final version

Implements #15's composite-variable %TYPE support and removal of bare type-name lookup. The commit additionally requires nnames == 2 for record lookup in plpgsql_parse_cwordtype() and expands block-qualified and schema-qualified regression coverage.

  • Pavel Stehulesaw an earlier versionLLM analysis, 97% surePavel endorsed the attached cleanup with +1 in #16 before commit, but the committed version subsequently tightened record-name lookup.
In plpgsql, allow %TYPE and %ROWTYPE to be followed by array decoration.
4 Jan 2024Tom Lanemaster17beta1REL_19_STABLE17beta1REL_18_STABLE17beta1REL_17_STABLE17beta1
LLM analysis, 100% suremodified before commitlight changesfrom patchset #141 of 1 reviewer saw the final version

Matches #14's array-decoration implementation, with editorial changes, helper renaming, equivalent loop simplification, and tests moved to src/pl/plpgsql/src/sql/plpgsql_array.sql. The commit credits Quan Zongliang and Pavel Stehule jointly, and Tom confirms the editorial changes in #15.

  • Tom Lanesaw the final versioncommittercommitted the patch

Credits across 2 commits

Author
Quan ZongliangLLM1
Tom LaneLLM1
Reviewer
Tom Lanecommitter1
Committer
Tom Lane2

N LLM means N of the credits come from LLM analysis, not from commit trailers.