I upgraded a busy pgpool-II instance to 3.0 last week and very quickly had to
back it out to 2.3.3 due to this issue. I tried 3.0.1 today and it does the
same thing.
Certain queries seem to be causing the backend to remain in the PARSE state.
The pgpool process itself leaves the socket open
I'm using Postgresql 9.0 and the latest pgpool from CVS Head from
Thursday October 21st, for streaming replication.
When I start pgpool-II, and see the postgresql log file, its output
states that pgpool_walrecrunning() can not access
'$libdir/pgpool_walrecrunning': No such file or
I upgraded a busy pgpool-II instance to 3.0 last week and very quickly had to
back it out to 2.3.3 due to this issue. I tried 3.0.1 today and it does the
same thing.
Certain queries seem to be causing the backend to remain in the PARSE state.
The pgpool process itself leaves the socket
I'm using Postgresql 9.0 and the latest pgpool from CVS Head from
Thursday October 21st, for streaming replication.
When I start pgpool-II, and see the postgresql log file, its output
states that pgpool_walrecrunning() can not access
'$libdir/pgpool_walrecrunning': No such file or
From: daniel.cre...@l-3com.com
Subject: RE: [Pgpool-general] pgpool_walrecrunning not working from pgpool
connection
Date: Tue, 26 Oct 2010 19:15:00 -0400
Message-ID:
9e33f44949583b4597bda2d0604256700b88d...@fls-exchange.corp.sds.l-3com.com
I'm using Postgresql 9.0 and the latest pgpool from
