aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/complex.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2006-06-21 18:30:19 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2006-06-21 18:30:19 +0000
commit62ae14545b35798fcb51bfd0aa9b5038ad6a07ff (patch)
tree15bdbb7ec8c8edad6ca2973797b7196cd3a1d628 /src/tutorial/complex.c
parente582d2ee1a149502f49c7a337707b4a0f940a51d (diff)
downloadpostgresql-62ae14545b35798fcb51bfd0aa9b5038ad6a07ff.tar.gz
postgresql-62ae14545b35798fcb51bfd0aa9b5038ad6a07ff.zip
Disallow aggregate functions in UPDATE commands (unless within a sub-SELECT).
This is disallowed by the SQL spec because it doesn't have any very sensible interpretation. Historically Postgres has allowed it but behaved strangely. As of PG 8.1 a server crash is possible if the MIN/MAX index optimization gets applied; rather than try to "fix" that, it seems best to just enforce the spec restriction. Per report from Josh Drake and Alvaro Herrera.
Diffstat (limited to 'src/tutorial/complex.c')
0 files changed, 0 insertions, 0 deletions