[pgpool-general: 797] Re: Problem with pgpool when using SSL, for client/pgpool communication

Tatsuo Ishii ishii at postgresql.org
Tue Jul 24 08:29:03 JST 2012

> 1) the only live backend is 1.
> 	Correct.
>>> 2) using extended protocol.
> 	Yes, it's rails.
>>> 3) transaction state is 'T' (idle in transaction).
> 	Yes, pgpool thinks it's idle in transaction.  When I do a ps on the db backend, it says it's "BIND".
>>> It seems pgpool is wating for someting to come from frontend because
>>> there's no pending data in frontend buffer nor backend buffer. Pgpool
>>> just processed BIND message from frontend and pgpool waits for
>>> DESCRIBE or EXECUTE message to come from rontend.
> 	Well, it may be waiting, but it probably isn't doing it properly somehow, because when we point the same app directly at the backend db, it works fine, and when we turn off ssl, it works fine as well.

I have compared the pgpool's SSL code with PostgreSQL's. It seems our
code forget to retry when necessary. Can you please try included
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pool_ssl.c.patch
Type: text/x-patch
Size: 1229 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20120724/9155e1e4/attachment.bin>

More information about the pgpool-general mailing list