pgsql: Disallow aggregate functions in UPDATE commands (unless within a - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Disallow aggregate functions in UPDATE commands (unless within a
Date
Msg-id 20060621183019.DF08C9FA65C@postgresql.org
Whole thread Raw
List 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.

Tags:
----
REL8_1_STABLE

Modified Files:
--------------
    pgsql/src/backend/parser:
        analyze.c (r1.326.2.1 -> r1.326.2.2)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/analyze.c.diff?r1=1.326.2.1&r2=1.326.2.2)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Disallow aggregate functions in UPDATE commands (unless within a
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Remove ancient kluge that kept nodeAgg.c from crashing on UPDATEs