diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2006-06-21 18:30:11 +0000 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2006-06-21 18:30:11 +0000 |
commit | 1f5ca045a435bc6aa9c98d7296973925c5208add (patch) | |
tree | 0d72663e4a8fc19315b2a166ef0e6cc9369218cd /src/tools/backend | |
parent | e256bafaa2aec06dd9dc9493c4e600319ab11525 (diff) | |
download | postgresql-1f5ca045a435bc6aa9c98d7296973925c5208add.tar.gz postgresql-1f5ca045a435bc6aa9c98d7296973925c5208add.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/tools/backend')
0 files changed, 0 insertions, 0 deletions