Hello,
I encountered a problem with a pgpool installation. Pgpool failed and
detached a backend, but I don't know the reason because that particular
pgpool server is not writing to its log (problem with cronolog, and I
can't restart pgpool since its a live system).
What I did find was a suspi
On this same issue, I found that pgpool detected an error just before
failing a backend as a response to a COMMIT (this is on a different
setup than the one from my previous post). This is the relevant part
from the pgpool log:
2009-12-26 00:13:04 DEBUG: pid 16329: ReadyForQuery: transaction st
PostgreSQL, pgpool-II version?
Do you have self contained test case?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
> On this same issue, I found that pgpool detected an error just before
> failing a backend as a response to a COMMIT (this is on a different
> setup than the one from my previous post). This
pgpool-II version is 2.2.4 compiled against libpq 8.1.15, and postgres
version is 8.1.15.
Both run on Debian etch amd64.
I haven't been able to create a test case yet, but I've been able to
verify that it always happens after a COMMIT (like my previous example)
or a BEGIN.
Regards
On Wed,
I looked into this but couldn't find why pgpool-II sent 4 to
PostgreSQL. Any test case to reproduce the error please.
In the mean time I start to think that pgpool-II should not trigger
failover if failed to read data from backend. Looking into PostgreSQL
I found lots of places where FATAL errors
From what I've seen, only a PANIC error means that the postgres server
is down. I think a FATAL error should trigger a failover only if it's
received in response to an authentication attempt.
About the "type 4" message I think my client/frontend is sending the
corrupt messages (I still don't kn
I found out more about this situation. The 0x04 is always read after
receiving a terminate ('X') message from the frontend, which makes me
think that the frontend might be sending garbage after finishing the
session, or somehow reading the length of the terminate message
(0x0004) fails in lin
Thanks for analysis.
> I found out more about this situation. The 0x04 is always read after
> receiving a terminate ('X') message from the frontend, which makes me
> think that the frontend might be sending garbage after finishing the
> session, or somehow reading the length of the terminate mess
> From what I've seen, only a PANIC error means that the postgres server
> is down. I think a FATAL error should trigger a failover only if it's
> received in response to an authentication attempt.
>
> About the "type 4" message I think my client/frontend is sending the
> corrupt messages (I sti
