aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/enum.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2020-11-04 15:08:37 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2020-11-04 15:08:37 -0500
commit5c292e6b90433c760a3e15027646c7b94afd0cdd (patch)
treef7a22ff756c6234eb7c234aab6d4d60253847767 /src/backend/utils/adt/enum.c
parent40c24bfef92530bd846e111c1742c2a54441c62c (diff)
downloadpostgresql-5c292e6b90433c760a3e15027646c7b94afd0cdd.tar.gz
postgresql-5c292e6b90433c760a3e15027646c7b94afd0cdd.zip
Declare lead() and lag() using anycompatible not anyelement.
This allows use of a "default" expression that doesn't slavishly match the data column's type. Formerly you got something like "function lag(numeric, integer, integer) does not exist", which is not just unhelpful but actively misleading. The SQL spec suggests that the default should be coerced to the data column's type, but this implementation instead chooses the common supertype, which seems at least as reasonable. (Note: I took the opportunity to run "make reformat-dat-files" on pg_proc.dat, so this commit includes some cosmetic changes to recently-added entries that aren't related to lead/lag.) Vik Fearing Discussion: https://postgr.es/m/77675130-89da-dab1-51dd-492c93dcf5d1@postgresfriends.org
Diffstat (limited to 'src/backend/utils/adt/enum.c')
0 files changed, 0 insertions, 0 deletions