Re: BUG #11335: an invalid prepare statement causes crash at log_statement = 'mod' or 'ddl'.

On Tue, Sep 2, 2014 at 8:16 PM,  <harukat@sraoss.co.jp> wrote:
> The following bug has been logged on the website:
>
> Bug reference:      11335
> Logged by:          invalid prepare statement causes crash at log_statement = 'mod' or 'ddl'.
> Email address:      harukat@sraoss.co.jp
> PostgreSQL version: 9.3.5
> Operating system:   CentOS 6.2 (64bit / gcc 4.4.7)
> Description:
>
>
> setting:
>   log_statement = 'mod' # or 'ddl'
>
> reproduction client code:
>  <?php
>  require_once 'MDB2.php';
>  $con1 =& MDB2::connect("pgsql://postgres@localhost/db1");
>  if (PEAR::isError($con1)) { die($con1->getMessage()); }
>  $sth = $con1->prepare("");
>  if (PEAR::isError($sth)) { die($sth->getMessage()); }
>  $sth->execute();
>  ?>
>
> log messages:
>  2014-09-02 19:41:57 JST 9453 LOG:  server process (PID 10372) was
>  terminated by signal11: Segmentation fault
>  2014-09-02 19:41:57 JST 9453 DETAIL:  Failed process was running:
>  EXECUTE mdb2_statement_pgsql_9cc7dc53dfc30b3c2b937c650346f586
>
> This occur in 9.3.5 and 9.1.14. (It probably occur at any versions.)
> I tested that the following fix prevent this crash.

Thanks for reporting the bug! This segmentation fault could reproduce
even on my machine. Barring any objection, I will apply the change that
you suggested.

Regards,

--
Fujii Masao