From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: UPDATE crash in HEAD and 8.1 |
Date: | 2006-06-20 18:03:13 |
Message-ID: | 20060620180313.GW26882@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > update pk set id = max(id) + 2;
>
> I'm fairly sure this query is illegal per spec. There are ancient
> discussions in the archives about whether aggregates in an UPDATE target
> list can have a consistent interpretation or not. We never found one,
> but never got around to disallowing it either. Maybe it's time. If you
> try it with something like sum() you don't get a crash, but you do get
> rather bizarre behavior.
Yeah, I agree we should disallow it. For the curious, the bizarre behavior
is
alvherre=# update pk set id = count(id) ;
ERROR: ctid is NULL
alvherre=# update pk set id = sum(id) ;
ERROR: ctid is NULL
Clearly not a very useful error message.
> Having said that, this may well expose a bug in the MAX-optimization
> code that has consequences for more useful queries. I'll take a look
> later today if no one beats me to it.
I refrain -- tried following it but I don't know that code at all.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Wade Klaver | 2006-06-20 18:03:55 | Re: Initdb segfaults during "initializing pg_authid" |
Previous Message | Andrew Dunstan | 2006-06-20 17:48:59 | Re: UPDATE crash in HEAD and 8.1 |