[pgpool-general: 1006] Re: using prepared statements when memory_cache_enabled=on

[Lonni J Friedman]

On Fri, Sep 14, 2012 at 3:09 PM, Tatsuo Ishii <ishii at sraoss.co.jp> wrote:
>> On Thu, Sep 13, 2012 at 6:35 PM, Tatsuo Ishii <ishii at postgresql.org> wrote:
>>>> pg_* functions.  Stuff like pg_prepare, pg_exec, pg_query.
>>>
>>> Can you show us pg_prepare example? I'm interested in what statement
>>> names you are using.
>>
>> pg_prepare($db, $preparedStatementKey, "SELECT
>> id,pass,fail,filtercount,info,current_status,last_update,os,arch,branch,gpu,build_type,subtest,osversion
>> FROM cudasmoke WHERE (last_update > $1 AND last_update < $2) AND os=$3
>> AND arch=$4 AND branch=$5 AND build_type= $6 AND subtest=$7 AND
>> osversion=$8 AND gpu=$9 ORDER BY last_update DESC LIMIT 1" )
>
> So what's the content of $preparedStatementKey?

Its a unique identifier string for the prepared statement, comprised
of the concatenated sha1sum and md5sum of the prepared statement.

So it ends up looking something like this:
pg_execute($db,a1a3a2f461a0efc2eee2f60f940df6b77eb552f9f5a985165c3ab1665384fa9cce8b1b62,"SELECT
id,pass,fail,filtercount,info,current_status,last_update,os,arch,branch,gpu,build_type,subtest,osversion
FROM cudasmoke WHERE (last_update > $1 AND last_update < $2) AND os=$3
AND arch=$4 AND branch=$5 AND build_type= $6 AND subtest=$7 AND
osversion=$8 AND gpu=$9 ORDER BY last_update DESC LIMIT 1);