pgsql: If we're gonna check for array overrun, we really should do so

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: If we're gonna check for array overrun, we really should do so
Date: 2005-02-08 18:22:00
Message-ID: 20050208182200.52A688B9F87@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
If we're gonna check for array overrun, we really should do so before
overrunning the array, not after.

Tags:
----
REL8_0_STABLE

Modified Files:
--------------
pgsql/src/pl/plpgsql/src:
gram.y (r1.64.4.2 -> r1.64.4.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y.diff?r1=1.64.4.2&r2=1.64.4.3)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2005-02-08 18:22:19 pgsql: If we're gonna check for array overrun, we really should do so
Previous Message Bruce Momjian 2005-02-08 15:41:18 Re: [COMMITTERS] How I can add new function writing on C under Win32