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

Re: BUG #2236: extremely slow to get unescaped bytea data

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kalador Tech Support <support(at)kalador(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2236: extremely slow to get unescaped bytea data
Date: 2006-02-09 15:58:57
Message-ID: 20060209155857.GA38265@winnie.fuhr.org (view raw or flat)
Thread:
Lists: pgsql-bugs
On Thu, Feb 09, 2006 at 12:46:46PM -0300, Alvaro Herrera wrote:
> I note in the PHP 4 sources that the PQunescapeBytea function seems to
> have been copied there, "for the benefit of PostgreSQL 7.2 users".  It
> says that it comes from 7.3 but I don't see any sscanf call.
> 
> There is no PQunescapeBytea call in the whole source that I can see, so
> my guess is that the libpq function is not called at all.  So this may
> be a PHP bug rather than a Postgres bug.

The OP claimed to be using PHP 5.1.2, which does have a call to
PQunescapeBytea(), although it also has the old code you're seeing
and a HAVE_PQUNESCAPEBYTEA macro that determines which to use.

Interesting that the command line php and the Apache module behave
differently.  I wonder if ldd would show the php executable and
libphp5.so linked against different versions of libpq; that would
add weight to Tom's suggestion that an old libpq might be responsible.

-- 
Michael Fuhr

In response to

Responses

pgsql-bugs by date

Next:From: Kalador Tech SupportDate: 2006-02-09 16:40:32
Subject: Re: BUG #2236: extremely slow to get unescaped bytea data
Previous:From: Magnus HaganderDate: 2006-02-09 15:50:16
Subject: Re: BUG #2248: Fix for terminal server

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