Re: [COMMITTERS] pgsql: Repair incorrect check for coercion

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)postgresql(dot)org>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Repair incorrect check for coercion
Date: 2006-10-11 22:25:05
Message-ID: 200610112225.k9BMP5F01420@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:
> 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.

Does this mean if someone initdb's in a back branch, the regression
tests will start failing for them?

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2006-10-11 23:01:46 pgsql: Update pg_hba.conf comment about documentation section.
Previous Message Tom Lane 2006-10-11 20:56:32 pgsql: A bit of copy-editing on back-branch release notes.

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-10-11 22:26:50 Re: On status data and summaries
Previous Message Tom Lane 2006-10-11 22:24:31 Re: [GENERAL] strange error when inserting via a SRF into a table with a foreign key constraint