Hi,
I found what I think is a small error allocating memory in the
make_persistent_db_connection() function in child.c. The amount of
memory allocated is more than it should be, so it's actually harmless.
I attach a patch for it.
Regards
Index: child.c
===
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'am testing the disconnection of the backends configured to
replicate the querys, then i shutdown down the backend_hostname1 and
pgpool enter to degeneration mode ,ok this is the expected behavior and
the querys like insert are executed in the backend_hostname0 ok.
But if i shutdown
Hello,
Not sure if this will help. But i have created a database only for testing. It
contains simple structure but my results are still bad.
The table structure:
CREATE TABLE groups ( id INT NOT NULL , name VARCHAR( 50 ), PRIMARY KEY ( id )
);
CREATE TABLE users ( id INT NOT NULL, name VARC
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
