> Tatsuo,
>
> I'm excited that pgpool is working for us now. We plan to start using it in
> the near future on our production applications (hundreds of thousands of DB
> transactions per day). I have just a couple follow-up questions:
>
> 1. When we use pgpool, should we still use a databas
Thanks for the tip. The client_encoding and lc_messages values were different on the two databases. I fixed both settings, and it works now!
KevinTatsuo Ishii <[EMAIL PROTECTED]> wrote:
What are client_encoding values on these two servers? It seems they donot match...--Tatsuo Ishii> Sure, here
What are client_encoding values on these two servers? It seems they do
not match...
--
Tatsuo Ishii
> Sure, here is the debug output when I run the following command..
>
> -bash-2.05b$ psql -p -c 'show pool_status' template1
> psql: server closed the connection unexpectedly
> This p
Sure, here is the debug output when I run the following command..
-bash-2.05b$ psql -p -c 'show pool_status' template1psql: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request.
Debug output from
Can you show me debug messages by starting pgpool with -d option?
--
Tatsuo Ishii
> Hello,
>
> I'm having trouble getting pgpool to work in master/slave mode. I'm planning
> on using something like Slony-I for replication, and use pgpool only to load
> balance the queries across the master an
Hello,
I'm having trouble getting pgpool to work in master/slave mode. I'm planning on using something like Slony-I for replication, and use pgpool only to load balance the queries across the master and slave, as well as provide failover if the master goes down.
I configured the settings so r
