pgsql: Repair incorrect check for coercion of unknown literal to

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Repair incorrect check for coercion of unknown literal to
Date: 2006-10-11 20:21:28
Message-ID: 20061011202128.B75BD9FB41D@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Log Message:
-----------
Repair incorrect check for coercion of unknown literal to ANYARRAY, a bug
I introduced in 7.4.1 :-(. It's correct to allow unknown to be coerced to
ANY or ANYELEMENT, since it's a real-enough data type, but it most certainly
isn't an array datatype. This can cause a backend crash but AFAICT is not
exploitable as a security hole. Per report from Michael Fuhr.

Note: as fixed in HEAD, this changes a constant in the pg_stats view,
resulting in a change in the expected regression outputs. The back-branch
patches have been hacked to avoid that, so that pre-existing installations
won't start failing their regression tests.

Tags:
----
REL7_4_STABLE

Modified Files:
--------------
pgsql/src/backend/parser:
parse_coerce.c (r2.111.2.2 -> r2.111.2.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_coerce.c.diff?r1=2.111.2.2&r2=2.111.2.3)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2006-10-11 20:55:54 pgsql: A bit of copy-editing on back-branch release notes.
Previous Message Tom Lane 2006-10-11 20:21:19 pgsql: Repair incorrect check for coercion of unknown literal to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Sullivan 2006-10-11 20:27:41 On status data and summaries
Previous Message Theo Schlossnagle 2006-10-11 20:17:42 Re: Index Tuning Features