plproxy - plproxy: Fix argument value NULL check.

From: mkz(at)pgfoundry(dot)org (User Mkz)
To: pgsql-committers(at)postgresql(dot)org
Subject: plproxy - plproxy: Fix argument value NULL check.
Date: 2009-09-11 14:26:32
Message-ID: 20090911142632.8082B107207E@pgfoundry.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Fix argument value NULL check.

Incoming NULL value could cause crash in function containing SELECT
with different argument order. Due to thinko, NULL check was done
with query arg index, instead of function arg index.

Reported by João Matos

Modified Files:
--------------
plproxy/src:
execute.c (r1.16 -> r1.17)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plproxy/plproxy/src/execute.c?r1=1.16&r2=1.17)
plproxy/sql:
plproxy_select.sql (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plproxy/plproxy/sql/plproxy_select.sql?r1=1.3&r2=1.4)
plproxy/expected:
plproxy_select.out (r1.4 -> r1.5)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/plproxy/plproxy/expected/plproxy_select.out?r1=1.4&r2=1.5)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-09-11 14:51:36 Re: Re: [COMMITTERS] pgsql: On Windows, when a file is deleted and another process still has
Previous Message User Mkz 2009-09-11 14:23:59 plproxy - plproxy: Fix potential buffer overflow when len(typname) > 32