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

[Nozomi Anzai]

Hi,

> Greetings,
> I'm running 3.2.0 with memory_cache_enabled=on and memqcache_method =
> 'memcached', and I'm seeing really bizarre errors when using prepared
> statements.  Basically any query that should use the prepared
> statement is failing with:
> server sent data ("D" message) without prior row description ("T" message)
> 
> This only happens once the data has been cached by pgpool (with the
> memcache server).  If I set memory_cache_enabled=off, then it works
> fine.  I'm guessing that maybe the problem is that the prepared
> statement isn't getting cached, so the queries which depend on the
> prepared statement fail?
> 
> Is this expected behavior?  If so, is there a work around that doesn't
> require me to not cache the tables that the prepared statement
> reference?

I couldn't reproduce it by the following ways:

1) the attached simple Java program: pgsql.java (only executing one SELECT)
2) pgbench -M extended -f bench.sql

Which version is your PostgreSQL? I tested with pgpool-II 3.2.0
(officially released), PostgreSQL 9.1.0, and memcached 1.4.7.

> thanks!
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general


-- 
Nozomi Anzai
SRA OSS, Inc. Japan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgsql.java
Type: application/octet-stream
Size: 1737 bytes
Desc: not available
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20120905/7e4e5140/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bench.sql
Type: application/octet-stream
Size: 70 bytes
Desc: not available
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20120905/7e4e5140/attachment-0001.obj>