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

#1 (**permalink**) 04-12-2008, 06:15 AM

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@momjian.us
EnterpriseDB http://www.enterprisedb.com

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

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

#2 (**permalink**) 04-12-2008, 06:16 AM

Bruce Momjian <bruce@momjian.us> writes:
> Tom Lane wrote:
>> 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?

No.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode