--- On Thu, 12/8/10, Josh Berkus j...@agliodbs.com wrote:
Does anyone here combine pgpool and
pgbouncer?
If so, what order do you chain them in ... pgpool, then
multiple
pgbouncer pools, or pgbouncer in front of pgpool? And
why?
I'm thinking that pgbouncer in front of pgpool makes
Any ideas/suggestions?
-Original Message-
From: pgpool-general-boun...@pgfoundry.org
[mailto:pgpool-general-boun...@pgfoundry.org] On Behalf Of Gnanakumar
Sent: Tuesday, August 10, 2010 5:55 PM
To: pgpool-general@pgfoundry.org
Subject: [Pgpool-general] SQL statements not printed in pgpool
Interesting, but how would it reduce the number of connections pgpool needs
to deal with? Unless you can't get the pooling behaviour you want from
pgpool? Is it not pooling the connections in the way you want?
In your previous message you stated you needed up to 600 concurrent
Interesting. So once clients connects to pgbouncer, it keeps the
connection to clients. When a client starts a transaction, it connects
to PostgreSQL(or pgpool in your case). When a client finishes the
transaction, pgbouncer disconnects to PostgreSQL.
Actually, it doesn't disconnect. It
Any suggestions on how I can troubleshoot this? Very little diagnostic
data from pgpool appears to be available.
More on this: PCP thinks that node 1 is down:
pcp_node_info 10 localhost 9898 postgres postgres 1
db3 5432 3 1431655764.67
I don't know how it got this idea. There isn't
Any suggestions on how I can troubleshoot this? Very little diagnostic
data from pgpool appears to be available.
More on this: PCP thinks that node 1 is down:
pcp_node_info 10 localhost 9898 postgres postgres 1
db3 5432 3 1431655764.67
I don't know how it got this idea. There
Actually, it doesn't disconnect. It issues RESET ALL;DISCARD ALL; and
keeps the connection open, waiting for the next client transaction. It
only disconnects after a connection has been idle for a preset interval
(generally 5 minutes).
Ok. So if all clients are busy and keep on sending
No. I suspect bogus pgpool_status file is remained. Try:
Shudtown pgpool
Remove pgpool_status
Start pgpool
That appears to be the case. Is pgPool supposed to remove pgpool_status
when it shuts down?
This is normal. The value you see is the normalized value. From the
comment in
No. I suspect bogus pgpool_status file is remained. Try:
Shudtown pgpool
Remove pgpool_status
Start pgpool
That appears to be the case. Is pgPool supposed to remove pgpool_status
when it shuts down?
No. The reason why we have pgpool_status is to prevent from connecting
to the DB
Hmmm. You might want to display a more user-friendly value for the
user, though, no?
Good point:-) I'm thinking about to change it for coming 3.0.
Great! Might I also suggest using getopt-long for the PCP commands?
--
-- Josh Berkus
10 matches
Mail list logo
