aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeFunctionscan.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-04-23 21:21:12 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-04-23 21:21:12 -0400
commitf9cd2b7824f627069f81cbb47d767af039d66a0d (patch)
tree32a811c3acd28ec153cc14cdc5905f3cd0e67e21 /src/backend/executor/nodeFunctionscan.c
parent6c5cba8e0b0dee9d1802d3477b9b882782e95ab1 (diff)
downloadpostgresql-f9cd2b7824f627069f81cbb47d767af039d66a0d.tar.gz
postgresql-f9cd2b7824f627069f81cbb47d767af039d66a0d.zip
Fix incorrect pg_proc.proallargtypes entries for two built-in functions.
pg_sequence_parameters() and pg_identify_object() have had incorrect proallargtypes entries since 9.1 and 9.3 respectively. This was mostly masked by the correct information in proargtypes, but a few operations such as pg_get_function_arguments() (and thus psql's \df display) would show the wrong data types for these functions' input parameters. In HEAD, fix the wrong info, bump catversion, and add an opr_sanity regression test to catch future mistakes of this sort. In the back branches, just fix the wrong info so that installations initdb'd with future minor releases will have the right data. We can't force an initdb, and it doesn't seem like a good idea to add a regression test that will fail on existing installations. Andres Freund
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions