[Pgpool-hackers] Replication node failure == aborted transaction... bug?

[sean finney]

Hi folks,

While documenting and testing our local pgpool-II setup (replication
with load balancing), I came across something which i suspect may be
a bug.

I noticed that if i take one of the replication nodes offline, and if
the failure is noticed from a client transaction instead of a health
check, the failure propagates up to the client and causes an exception
(which in turn would likely cause a 500 Internal Server Error for
a visitor to a postgres-backed webapp).  Shouldn't it be the case that
the error results in the silent (to the frontend, anyway) degradation
of the node and another attempt at the transmission of the request?



	sean
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://pgfoundry.org/pipermail/pgpool-hackers/attachments/20100202/11943cd5/attachment.bin>