Any reasons why it's not possible to have pgpool split the multi-statement
query by using ;, and send one by one instead of making the client worry
about this?
Thanks,
-Daniel
-Original Message-
From: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-
-Original Message-
From: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-
boun...@pgfoundry.org] On Behalf Of Alan Hodgson
Sent: Thursday, October 06, 2011 5:52 PM
To: pgpool-general@pgfoundry.org
Subject: Re: [Pgpool-general] How to configure pgpool for pool
conexions..
So in the end, Server A and B are meant to be identical, right?
If so, you need multi-master replication. I think Bucardo is the one that can
do that.
-Daniel
From: pgpool-general-boun...@pgfoundry.org
[mailto:pgpool-general-boun...@pgfoundry.org] On Behalf Of Micka
Sent: Thursday,
Hi everyone,
I have configuration pgpool streaming replication load balancing
configuration with two nodes.
pgpool version is 3.1.0-alpha2 (hatsuiboshi), postgres on both nodes is
9.0.4
Reason why I have use this version is that latest stable version (at
that time) 3.0.1 was everything
You have to use pcp_attach_node command to re-attach that node. Pgpool
doesn't know if a database that went down is in good shape even if it is
back online. So, after you perform the synching (it seems like you did),
call the pcp_attach_node to bring it back to pgpool's pool of databases.
-Daniel
http://pgpool.projects.postgresql.org/pgpool-II/doc/pgpool-en.html
states the following:
backend_weight
... However, *values cannot be updated so you must restart pgpool-II in
that case*.
In pgpool-II 2.2.6/2.3 *or later, you can change this value by
re-loading the configuration file*.
According to Matt, he is using pgpool-II 3.0.4 built from source. I have
not tried either.
From: pgpool-general-boun...@pgfoundry.org
[mailto:pgpool-general-boun...@pgfoundry.org] On Behalf Of Anton Koldaev
Sent: Friday, June 17, 2011 2:39 PM
To: Matt Solnit
Cc: pgpool-general@pgfoundry.org
I think there is a misunderstanding...
To clarify (just in case).
1. Pgpool detects non-healthy postgresql backend.
2. Pgpool executes WHATEVER is in failover_command entry in
pgpool.conf
3. The end.
In failover_command you can put
executeFailoverOfMyCurrentSlavePostgreSqlBackend.sh.
Which
Try running pgpool -d -n, and search for failover_command. It should
tell you if was or not executed. Remember to enable health_check in
pgpool.conf. Search for health_check param in pgpool.conf.
-Daniel
From: Armin Nesiren [mailto:armin.nesi...@intera.si]
Sent: Friday, January 28, 2011
failover_command entry in pgpool.conf allows you to do whatever you need to
do when pgpool detects a database node degeneration. In your case you would
need to touch the file where PostgreSQL 9.0+ expects it (specified in
trigger_file within recovery.conf). Take a look at how postgresql 9.0's
Hi,
Using Master/Slave with Streaming Replication and Hot Standby, on
Failover, I think it would be a good idea to have pgpool stop handling
connections until new master becomes writable. Maybe, the application
should handle this, but we don't want the application check if the
database is
Hi all,
When doing a failover, shoudn't pgpool-II keep the new master as the
master from that point on?
From my experience, after the master database fails and the slave takes
over as master, if pcp_recovery_node is used to recover the old master,
pgpool-II is assumes the master is back
Issuing:
psql -h 10.20.60.2 -U someuser -p 5432 -c select
pgpool_walrecrunning() db0
Returns:
pgpool_walrecrunning
--
f
(1 row)
Thanks. What does this show?
psql -h 10.20.60.3 -U someuser -p 5432 -c select
pgpool_walrecrunning() db0
Same error:
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 suggest you to read this:
http://www.postgresql.org/docs/9.0/interactive/different-replication-
solutions.html
I would look at what Bucardo offers, which is asynchronous multi-
master
replication. In synchronous multi-master, and especially in your
case
with
pgpool-II, if
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 directory.
I suggest you to read this:
http://www.postgresql.org/docs/9.0/interactive/different-replication-sol
utions.html
I would look at what Bucardo offers, which is asynchronous multi-master
replication. In synchronous multi-master, and especially in your case
with pgpool-II, if one database goes
* 2 DB Servers (DB0 and DB1)
* 1 pgpool instance (in a thrid server)
* Streaming replication from DB0 (master) to DB1 (slave)
* If DB0 fails, DB1 must become primary.
Easy.
* As soon as DB0 is ready again, make it slave of DB1.
white_function_list
... In master slave mode, SELECTs are sent to master(primary) only.
(Taken from pgpool-II web site)
Is this true? What about when working with streaming replication where I
want the hot-standby to run read-only queries (SELECTs)?
Daniel
Hi,
As far as I know, pgpool-II waits for [all] backends to commit the SQL
statements (under replication mode) before returning to the client,
right? This means that if, for example, one of the backends is very busy
(100% CPU, etc.), pgpool will experience a delay and so will the
application.
I have health check enabled every 5 seconds or so, but most of the time
(if not always) I experience a failed attempt to connect (or execute a
query in an already started session), then, the next attempt succeeds.
So I think it is not working for me for avoiding the connection attempt
failure.
I forgot to specify that this happens after, for example,
backend_hostname0 is killed.
-Original Message-
From: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-
boun...@pgfoundry.org] On Behalf Of Crespo, Daniel @ SDS
Sent: Friday, June 18, 2010 9:49 AM
To: Joe Conway;
Here is a complement for that suggestion:
If the statement is INSERT/UPDATE/DELETE, and the number of returned
affected rows differ, degenerate the backends that differ from master
db, without throwing an error to the client (conserve transparency).
Daniel
-Original Message-
From:
I totally support this idea.
-Original Message-
From: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-
boun...@pgfoundry.org] On Behalf Of Tatsuo Ishii
Sent: Thursday, June 03, 2010 7:05 PM
To: a...@lingnu.com
Cc: tirt...@simply-y.com; pgpool-general@pgfoundry.org
Russ,
pgpool-II can call a script every time there is a failover event (see
'failover_command' in the manual). You can create a script that calls
pcp_node_attach to reattach the failed node once the access to it is
recovered. For example, keep testing SELECT 1; against the remote
database until
I think you are talking about table partitioning (not replication),
which I think it's supported by pgpool.
Daniel
-Original Message-
From: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-
boun...@pgfoundry.org] On Behalf Of Alessio Grasso
Sent: Wednesday, March 31, 2010
Question: What would happen if the multi-statement string is BEGIN; SELECT 1;
INSERT INTO ...; COMMIT;?
-Original Message-
From: Matthias Tief [mailto:matth...@itso-berlin.de]
Sent: Wednesday, March 10, 2010 7:21 AM
To: Tatsuo Ishii
Cc: cmart...@gmail.com; glynast...@yahoo.co.uk;
My experience is also that multi-statement queries (statement1; statement2;
...; statementN;) work in pgpool-II, so now I'm confused with pgpool-II
cannot process multi-statement query. Also, why wouldn't it work if PostgreSQL
itself does? I think the idea is pgpool-II to work transparently as
My other question is, the maintenance tasks reindex and vacuum,
should be
made over pgpool or over each backend?
Vaccuum with verbose option should not be used over pgpool. It may
cause kind mismatch error because number of messages returned from
vacuum may vary on each backend(I have a
Hi,
I'm using pgpool-II 2.2.2. I password protected the database for every
user, including 'postgres'. However, I made the .pgpass in the
corresponding home directories in order to have access without
explicitly providing password. If I password protect postgresql (by
changing pg_hba.conf of
Mary Ellen Fitzpatrick wrote:
Hi,
I am new at using pgpool and I am having some difficulty with
getting
pgpool/postgres to work on port . I am running CentOS5,
Postgres-8.1.18, and have installed pgpool-II-2.3.1. Even after
having
read the pgpool-II manual, pgpool-II-Tutorial
Hi!
i have a question about system_db.sql script included in pgpool.
Really is needed execute this script for pgpool to replicate???
Which is the best database to install it??? template1?? postgres???
ok! maybe the question was a too newbie :-) , but i hope your
answers
have
Hi,
I'm using pgpool 2.2.2. and wanted to know if the following is expected
behavior.
Configuration:
+-+
| (Server A) |
| App --- pgpool - backend0 |
+\+
\
Hi!
i have this trouble with pgpool-II 2.2.6 and start_recovery.
when i tried to recover a node whit this command:
pcp_recovery_node 5 pgsql1 9898 root rutilio 1
and the log of pgpool is:
2010-01-27 09:24:12 LOG: pid 6036: CHECKPOINT in the 1st stage done
2010-01-27
Hi,
I'm using pgpool 2.2.2 connecting to two backends PGSQL8.2.1. Below is a
diagram of my configuration
.--- backend0
/
App --- pgpool
\
`--- backend1
Where App, for testing purposes is:
while [ 1 ]; do psql -U postgres -p
Sorry, I missed one step in the series:
The problem is as follows:
1. pgpool is stopped
2. App is started
Every 0.01 secs, outputs:
psql: could not connect to server: Connection refused
Is the server running locally and accepting
connections on Unix domain
I'm also getting this exact behavior. Any clue?
Thanks,
Daniel
-Original Message-
From: pgpool-general-boun...@pgfoundry.org [mailto:pgpool-general-
boun...@pgfoundry.org] On Behalf Of Ger Apeldoorn
Sent: Thursday, January 14, 2010 2:56 AM
To: pgpool-general@pgfoundry.org
Subject:
In addition to that, I would say that first of all, you need to know
what you need: Synchronous replication or Asynchronous replication.
Slony-I is Asynchronous
Pgpool-II is Synchronous
You should not compare Slony-I vs Pgpool-II.
Daniel
From: pgpool-general-boun...@pgfoundry.org
Hi Fernando,
Thanks for the info. Oh, pgpool's recovery process connects to
template1. That was the cause of the problem. Pgpool should connects
to postgres database instead of template1, I think. Will fix.
--
Tatsuo Ishii
Was this introduced in 2.3.x or is this same behavior occurring on
If pgpool-ii is restarted, it will consider that all backends
are
in
good
state - even if one of the backends was not up to date (and data
was
not
being replicated there).
What is the best way to preserve backend state across pgpool-ii
restarts?
IMHO, making
If pgpool-ii is restarted, it will consider that all backends are in
good state - even if one of the backends was not up to date (and
data
was not being replicated there).
What is the best way to preserve backend state across pgpool-ii
restarts?
I'm also interested in knowing this
If pgpool-ii is restarted, it will consider that all backends are in
good
state - even if one of the backends was not up to date (and data was
not
being replicated there).
What is the best way to preserve backend state across pgpool-ii
restarts?
IMHO, making sure the PostgreSQL
There are two problems with the SQL created by pgAdmin:
- multi statement (two or more SQLs per 1 line)
Running select 1; select 2; into pgpool will cause a problem?
What is the point of not being able to execute multi-statements?
Daniel
___
2009-09-15 12:04:00 LOG: pid 3983: starting recovery command:
SELECT
pgpool_recovery('startbackup1', 'back2',
'/var/lib/postgresql/8.3/main')
2009-09-15 12:04:00 DEBUG: pid 3983: exec_recovery: start recovery
2009-09-15 12:04:00 ERROR: pid 3983: exec_recovery: startbackup1
command
failed
Im using pgpool for 3 backends that have different weights. Its a
replication/load-balancing setup. Is there any way to show the
number
of
connections/queries that have been sent to each of the backends? I
just want
to verify that the weighing mechanism works correctly.
Check the
Are you able to create a table running slony-I (without using pgpool)?
AFAIK, you can not create tables by issuing SQL statements to an open
session of postgresql when it's being replicated by slony-I.
Daniel
From: pgpool-general-boun...@pgfoundry.org
Hi,
I think vacuum works properly, but just in case I ask: is there any
limitations when running vacuum; within a pgpool-II session?
Thanks,
Daniel
___
Pgpool-general mailing list
Pgpool-general@pgfoundry.org
Notice in the second case it is using localhost as the parameter
(and localhost is not the node I'm trying to recover). I notice that if
I start pgpool with only one backend, then I add a backend to the conf
file, then do pgpool reload, it does read it correctly, eg, I see
I think you should
Yes. Look for the following keywords:
pcp_recovery_node (pgpool client program)
client_idle_limit_in_recovery (parameter in pgpool.conf)
pgpool_copy_backup (script)
pgpool_switch_xlog (script)
pgpool_remote_start (script)
Daniel
From:
Let's say you have two backends: backend0 and backend1. Supposing
backend1 has failed, recoverying it (by re-synchronizing data from
backend0) is expected to have a pgpool client reconnection. From the
point of view of pgpool, the clients must disconnect and reconnect in
order to complete a data
You are welcome.
So this is done by using pcp_recovery_node command?
Yes. That command will trigger everything I explained. Also, be aware
that your database needs to have the pgpool stored procedures installed
in order for it to work. And for them to be installed, your database
needs to
Any news on this? I have checked it on pgpool-II 2.2beta1 and still
happens. Any workaround or suggestions?
Thanks,
Daniel
-Original Message-
From: pgpool-general-boun...@pgfoundry.org
[mailto:pgpool-general-boun...@pgfoundry.org] On Behalf Of
Jaume Sabater
Sent: Friday, January
Hi, Gerd.
I'm interested. Thanks!
Daniel
-Original Message-
From: pgpool-general-boun...@pgfoundry.org
[mailto:pgpool-general-boun...@pgfoundry.org] On Behalf Of Gerd König
Sent: Wednesday, February 18, 2009 7:45 AM
To: pgpool-general@pgfoundry.org
Subject: [Pgpool-general]
Exactly :)
-Original Message-
From: Glyn Astill [mailto:glynast...@yahoo.co.uk]
Sent: Wednesday, February 18, 2009 9:51 AM
To: Gerd König; pgpool-general@pgfoundry.org; Crespo, Daniel @ SDS
Subject: Re: [Pgpool-general] documentation for beginners
Yeah,
Although our pool is
The defaulted value of nobody is for health_check_user in pgpool.conf,
and must exist as a postgresql user in the backends. I changed it to
postgres, and works fine. I don't use system_db, so I don't need a user
for it. It's a matter of having the users in the backend engines, that's
all.
Daniel
Hi, Jaume
I'm also interested in having that tutorial. Is it possible for you to send the
URL to me as well?
Thanks!
Daniel
-Original Message-
From: pgpool-general-boun...@pgfoundry.org
[mailto:pgpool-general-boun...@pgfoundry.org] On Behalf Of
Jaume Sabater
Sent: Wednesday,
Hello, list.
I'm finally using the latest CVS version of pgpool-II. One question: is
it proper to leave the creation of pgpool.pid under /tmp directory? I
suppose it is defaulted to /tmp for suiting everybody's needs... Any
thoughts?
Thanks,
Daniel
Thanks for your response, I really appreciate it.
First, I don't really agree on just attaching a node back into the
pool the manner your are doing with the steps shown below. If a
postgreSQL backend node goes down, for some reason out of anyone's
control, you should bring that node
I have some good and bad news in the my testings of 2.1 release (since
the latest CVS version does not work for me. Maybe this helps a bit):
The good news:
---
The connection blocking behavior I had when a failover happened was
because the failover_command was not returning (in
Sorry for the delay, I haven't had enough time.
1. Show us the logs. Full logs, but only the relevant parts (got tons
of things to read every day here). :)
I'll try it again with full logs to give them to you guys
2. Check whether PostgreSQL is having some problem of some sort before
Thanks, Jaume...
How can I know the list of all the files that are to be removed without
having to go through the make files?
-Original Message-
From: pgpool-general-boun...@pgfoundry.org
[mailto:pgpool-general-boun...@pgfoundry.org] On Behalf Of Jaume Sabater
Sent: Thursday, January 08,
Finally, I installed the latest CVS checkout. I uninstalled my previous
pgpool-II build by doing:
[root ~]# make uninstall
[user ~]# make clean
Then, went to the just downloaded repository for pgpool-II and did:
[user ~]# ./configure
[user ~]# make
[root ~]# make install
Tried the below same
Thanks for sharing!
I have similar scripts to copy-base-backup and pgpool-start-remote. I
think I'm not needing pgpool-recovery-pitr. Am I wrong or the pitr one
is in case I don't use a two stages recovery?
Thanks,
Daniel
-Original Message-
From: pgpool-general-boun...@pgfoundry.org
Hello,
I have the exact same doubt. However, in my system, appservers A and
B don't run at the same time. While A is active, B is inactive and
viceversa. In the case A becomes unavailable, B takes over. So, the
scenario in this case would be:
Pgpool in both appservers are running and connected
64 matches
Mail list logo
