pgsql: Disallow aggregate functions in UPDATE commands (unless within a

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Disallow aggregate functions in UPDATE commands (unless within a
Date: 2006-06-21 18:30:11
Message-ID: 20060621183011.91B659FB1BC@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
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.

Modified Files:
--------------
pgsql/src/backend/parser:
analyze.c (r1.334 -> r1.335)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/analyze.c.diff?r1=1.334&r2=1.335)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2006-06-21 18:30:19 pgsql: Disallow aggregate functions in UPDATE commands (unless within a
Previous Message Tom Lane 2006-06-21 18:09:53 pgsql: Eliminate a gratuitously different wording of the 'cannot use