Skip site navigation (1) Skip section navigation (2)

pgsql: Fix a passel of ancient bugs in to_char(), including two distinct

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix a passel of ancient bugs in to_char(), including two distinct
Date: 2007-06-29 01:51:49
Message-ID: 20070629015149.DD9709FB99C@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Fix a passel of ancient bugs in to_char(), including two distinct buffer
overruns (neither of which seem likely to be exploitable as security holes,
fortunately, since the provoker can't control the data written).  One of
these is due to choosing to stomp on the output of a called function, which
is bad news in any case; make it treat the called functions' results as
read-only.  Avoid some unnecessary palloc/pfree traffic too; it's not
really helpful to free small temporary objects, and again this is presuming
more than it ought to about the nature of the results of called functions.
Per report from Patrick Welche and additional code-reading by Imad.

Tags:
----
REL8_2_STABLE

Modified Files:
--------------
    pgsql/src/backend/utils/adt:
        formatting.c (r1.116.2.2 -> r1.116.2.3)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/formatting.c.diff?r1=1.116.2.2&r2=1.116.2.3)

pgsql-committers by date

Next:From: Tom LaneDate: 2007-06-29 01:51:56
Subject: pgsql: Fix a passel of ancient bugs in to_char(), including two distinct
Previous:From: Tom LaneDate: 2007-06-29 01:51:35
Subject: pgsql: Fix a passel of ancient bugs in to_char(), including two distinct

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group