diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2025-04-03 16:03:06 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2025-04-03 16:03:12 -0400 |
commit | dbd437e670b88ca67f6b2477e853412a0e82a8cc (patch) | |
tree | addd72e99f1262b338e9d0f33f826a5fd024af6f /src/backend/access/gist/gistvacuum.c | |
parent | 46c4c7cbc6d562d5f1b784fea9527c998c190b99 (diff) | |
download | postgresql-dbd437e670b88ca67f6b2477e853412a0e82a8cc.tar.gz postgresql-dbd437e670b88ca67f6b2477e853412a0e82a8cc.zip |
Fix oversight in commit 0dca5d68d.
As coded, fmgr_sql() would get an assertion failure for a SQL function
that has an empty body and is declared to return some type other than
VOID. Typically you'd never get that far because fmgr_sql_validator()
would reject such a definition (I suspect that's how come I managed to
miss the bug). But if check_function_bodies is off or the function is
polymorphic, the validation check wouldn't get made.
Reported-by: Alexander Lakhin <exclusion@gmail.com>
Author: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/0fde377a-3870-4d18-946a-ce008ee5bb88@gmail.com
Diffstat (limited to 'src/backend/access/gist/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions