On 05/02/11 11:26, Gary Fu wrote:
Hi,
I'm running pgpool2 3.0.1 with replication mode on two postgresql
9.0.4 db servers (updated from 8.4.4). I have the 'replicate_select'
and 'replication_stop_on_mismatch' both set to 'true'.
I just noticed that under psql, if I cancel a long select sql
On 01/18/11 19:56, Tatsuo Ishii wrote:
Sorry, now I understand fail over caused by the \d command problem is
due to the replicate_select is set. My question now is how to
replicate a select function (with insert/update) when replicate_select
is disabled. It looks like that we can use
On 01/17/11 19:45, Tatsuo Ishii wrote:
Is there a simple query (not the 'show' command) to tell if my current
db connection is using pgpool ?
No. Why is show pool_status not good?
It causes error when the connection is not using pgpool.
___
Yes, do you mean that I have to disable it ? As far as I know, our
application may fail over with it disabled.
Thanks,
Gary
Are you enabling replicate_select?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
Hi,
I
On 01/18/11 15:35, Guillaume Lelarge wrote:
Le 18/01/2011 16:16, Gary Fu a écrit :
On 01/17/11 19:45, Tatsuo Ishii wrote:
Is there a simple query (not the 'show' command) to tell if my current
db connection is using pgpool ?
No. Why is show pool_status not good?
It causes error when
On 01/18/11 18:02, Tatsuo Ishii wrote:
If you still have an error in spite of disabling replicate_select,
please let me know details (pgpool.conf, pgpool-II version).
I think the problem is with the function with insert/update sqls in
it, if the replicate_select is off and I use 'select
Hi,
Is there a simple query (not the 'show' command) to tell if my current
db connection is using pgpool ?
Thanks,
Gary
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
http://pgfoundry.org/mailman/listinfo/pgpool-general
Hi,
I noticed that sometimes the psql command '\d' (or other commands) will
cause the pgpool (with replication mode) fail over due to the specific
'oid' is used in the join. Is there any solution/suggestion how to
avoid this ?
Thanks,
Gary
2011-01-17 17:15:44 ERROR: pid 13320:
Hi Tatsuo,
I'm running pgpool2 version 3.0 and have the following setup:
replication_stop_on_mismatch = true
failover_if_affected_tuples_mismatch = true
replicate_select = false
However, from the following example, I'm not sure why there is no
failover happen when the update sql fails
On 10/04/10 18:56, Tatsuo Ishii wrote:
I'm running pgpool2 3.0 with replication mode. I just noticed that
when
the pgpool failover (due to mismatch error) is done by shutting down
the
secondary db, my application failed due to the lost of connection.
The documentation mention that when the
Hi,
I'm running pgpool2 3.0 with replication mode. I just noticed that when
the pgpool failover (due to mismatch error) is done by shutting down the
secondary db, my application failed due to the lost of connection.
The documentation mention that when the failover is performed,
pgpool kills all
On 09/29/10 20:04, Tatsuo Ishii wrote:
On 09/28/10 19:19, Tatsuo Ishii wrote:
When I started the pgpool2 (version 3.0 on CentOS, with user
'sd3ops1', not 'postgres') on a host different from the two db hosts,
I noticed that the log always failed on health_check on node 1 db with
the
Hi,
When I started the pgpool2 (version 3.0 on CentOS, with user 'sd3ops1',
not 'postgres') on a host different from the two db hosts, I noticed
that the log always failed on health_check on node 1 db with the
following message (without any client connection yet):
health_check: 0 th DB
Tatsuo,
I tried the patch for 'configure.in' without rebuilding 8.4.4 with SSL
and still
got the same error.
I'll have SA to rebuild the 8.4.4 with SSL support to see what happen.
Thanks,
Gary
After more investigation, I found serious problem with pgpool's
configure script if SSL is
Hi,
After upgraded postgresql from 8.4.2 to 8.4.4, I have problem to run the
pgool II 2.3.3 with the following error message:
/pgpool: symbol lookup error: /usr/local/pgsql/lib/libpq.so.5: undefined
symbol: dlopen
When I tried to rebuild the pgpool II 2.3.3, the 'configure' failed with
Hi,
I have pgpool2 2.0.1 running on linux with two backend postgresql 8.2.6
servers,
one with the pgpool2 and the other one is on another linux box.
I tried pgadmin from a pc to connect the pgpool through the ssh
tunneling without
problem on select/update/insert sql. A simple java program
I could not reproduce your problem here. Can you show me pgpool.conf?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
Hi,
In pgpool-II 2.0.1, when the health check is turned on
(health_check_period = 30), the following
extra logs will be logged in the db servers. Any way to disable those
17 matches
Mail list logo
