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:05 |
Message-ID: | 20061011202105.10F9C9FB3AD@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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.
Modified Files:
--------------
pgsql/src/backend/parser:
parse_coerce.c (r2.144 -> r2.145)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_coerce.c.diff?r1=2.144&r2=2.145)
pgsql/src/test/regress/expected:
rules.out (r1.119 -> r1.120)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/rules.out.diff?r1=1.119&r2=1.120)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-10-11 20:21:11 | pgsql: Repair incorrect check for coercion of unknown literal to |
Previous Message | Tom Lane | 2006-10-11 20:03:26 | pgsql: CREATE TABLE ... |