aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonfuncs.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2022-02-24 16:11:34 +0900
committerMichael Paquier <michael@paquier.xyz>2022-02-24 16:11:34 +0900
commitfcc28178c6943d7df72b484a87fdb7e06d0c1079 (patch)
tree29d84d92aa610c56a1c1c1a4089d9e5fd201e0ba /src/backend/utils/adt/jsonfuncs.c
parent04e706d4238f98a98e1c0b1a02db9d4280b96f04 (diff)
downloadpostgresql-fcc28178c6943d7df72b484a87fdb7e06d0c1079.tar.gz
postgresql-fcc28178c6943d7df72b484a87fdb7e06d0c1079.zip
Clean up and simplify code in a couple of set-returning functions
The following set-returning functions have their logic simplified, to be more consistent with other in-core areas: - pg_prepared_statement()'s tuple descriptor is now created with get_call_result_type() instead of being created from scratch, saving from some duplication with pg_proc.dat. - show_all_file_settings(), similarly, now uses get_call_result_type() to build its tuple descriptor instead of creating it from scratch. - pg_options_to_table() made use of a static routine called only once. This commit removes this internal routine to make the function easier to follow. - pg_config() was using a unique logic style, doing checks on the tuple descriptor passed down in expectedDesc, but it has no need to do so. This switches the function to use a tuplestore with a tuple descriptor retrieved from get_call_result_type(), instead. This simplifies an upcoming patch aimed at refactoring the way tuplestores are created and checked in set-returning functions, this change making sense as its own independent cleanup by shaving some code. Author: Melanie Plageman, Michael Paquier Reviewed-by: Justin Pryzby Discussion: https://postgr.es/m/CAAKRu_azyd1Z3W_r7Ou4sorTjRCs+PxeHw1CWJeXKofkE6TuZg@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions