Am 15.06.2017 um 11:57 schrieb Martin Goodson:
The issues I think I would have with pgbouncer at the application
level is ...
1) What if an application server is down when pgbouncer tries to
update where the database IP is pointing to? When it is brought back
into service could that crea
On 15/06/2017 05:27, Andreas Kretschmer wrote:
Am 15.06.2017 um 01:18 schrieb Martin Goodson:
I'm just wondering how people may have implemented this. Do people
setup pgbouncer nodes on the database servers themselves, on
application servers, in the middle tier between the application and
Am 15.06.2017 um 08:26 schrieb Rory Campbell-Lange:
On 15/06/17, Andreas Kretschmer (andr...@a-kretschmer.de) wrote:
Am 15.06.2017 um 01:18 schrieb Martin Goodson:
...Do people setup pgbouncer nodes on the database servers
themselves, on application servers, in the middle tier between the
app
On 15/06/17, Andreas Kretschmer (andr...@a-kretschmer.de) wrote:
>
> Am 15.06.2017 um 01:18 schrieb Martin Goodson:
> >
> >...Do people setup pgbouncer nodes on the database servers
> >themselves, on application servers, in the middle tier between the
> >application and database, and so forth, or
On 15/06/17, Martin Goodson (kaema...@googlemail.com) wrote:
> On 14/06/2017 19:54, Rory Campbell-Lange wrote:
> >On 14/06/17, Martin Goodson (kaema...@googlemail.com) wrote:
> >>The new master's repmgr promote script will execute commands to pause
> >>pgbouncer, reconfigure pgbouncer to point to t
Am 15.06.2017 um 01:18 schrieb Martin Goodson:
I'm just wondering how people may have implemented this. Do people
setup pgbouncer nodes on the database servers themselves, on
application servers, in the middle tier between the application and
database, and so forth, or some combination of
On 14/06/2017 19:54, Rory Campbell-Lange wrote:
On 14/06/17, Martin Goodson (kaema...@googlemail.com) wrote:
The new master's repmgr promote script will execute commands to pause
pgbouncer, reconfigure pgbouncer to point to the new database address, and
then resume.
You could just move the ser
On 14/06/17, Martin Goodson (kaema...@googlemail.com) wrote:
> The new master's repmgr promote script will execute commands to pause
> pgbouncer, reconfigure pgbouncer to point to the new database address, and
> then resume.
You could just move the service ip address at the new postgresql master
t
Hello.
Currently we're running all our PostgreSQL databases on ESX Stretch
Clusters, but our company is looking at moving away from those to a
private cloud solution.
I'm informed that, going forward, new servers provisioned for us to
install PostgreSQL databases on will be entirely isolated
Email.
Original Message
Subject: Re: [GENERAL] repmgr cascade replication node delay
Local Time: June 1, 2017 11:42 PM
UTC Time: June 1, 2017 10:42 PM
From: david.g.johns...@gmail.com
To: Juliano
pgsql-general@postgresql.org ,
pgsql-general-ow...@postgresql.org
On Thu, Jun 1
On Thu, Jun 1, 2017 at 3:30 PM, Juliano wrote:
> The objective of an extra node 24 hours delayed is to recover some error
> in the server.
> Is it possible to make this configuration?
>
A quick search turns up:
recovery_min_apply_delay
https://www.postgresql.org/docs/current/static/standby-
Hi guys,
I have a replication scenario master/slave and I would like to create one extra
more node (cascade from slave) with a time delay of 24-hour replication.
The objective of an extra node 24 hours delayed is to recover some error in the
server.
Is it possible to make this configuration?
Hi guys,
I'd like to insert a new standby node without clone the data of the master, how
is it possible?
Explain: Register a new slave node on the cluster and avoid copy 2TB of data by
network, so it comes with the clone data on the disk. After this I think just
increment the new data with --r
Hello
I have a three node postgresql 9.4 cluster configured with one standby in
sync mode and the other in asynch mode.
If the master datbase is shutdown the pg promote happens as expected.
However on the remaining standby node the RECOVERY.CONF file is
misconfigured when issuing the command:
Re
On 01/28/2016 08:02 PM, John R Pierce wrote:
> I go to read the repmgr quickstart and get a 404?
> https://github.com/2ndQuadrant/repmgr/blob/master/QUICKSTART.md
>
> I was on this page yesterday and it was fine.
The documentation was refactored and everything was put in the README.
https://githu
I go to read the repmgr quickstart and get a 404?
https://github.com/2ndQuadrant/repmgr/blob/master/QUICKSTART.md
I was on this page yesterday and it was fine.
--
john r pierce, recycling bits in santa cruz
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes
Hey,
Thanks for the reply, this helped me very much.
Kind Regards,
Aviel Buskila.
בתאריך 17 באוג' 2015 08:49, "Jony Cohen" כתב:
> Hi,
> The clone command just clones the data from node2 to node1, you need to
> also register it with the `force` option to override the old record. (as if
> you're b
Hi,
The clone command just clones the data from node2 to node1, you need to
also register it with the `force` option to override the old record. (as if
you're building a new replica node...)
see:
https://github.com/2ndQuadrant/repmgr#converting-a-failed-master-to-a-standby
Regards,
- Jony
On Su
Hey,
I think I know what the problem is,
after the first failover when I clone the old master to be standby with the
'repmgr standby clone' command it seems that nothing updates the repl_nodes
table with the new standby in my cluster so on the next failover the
repmgrd is failed to find a new upcom
hey,
I have tried to set the configuration all over again, now the status of
'repl_nodes' before the failover is:
id | type | upstream_node_id | cluster | name | conninfo | priority | active
+-+---++--+---
El 14/08/15 a las 04:14, Aviel Buskila escribió:
> Hey,
> yes I did .. and still it wont fail back..
Can you send over the output of "repmgr cluster show" before and after
the failover process?
The output of SELECT * FROM repmgr_schema.repl_nodes; after the failover
(you need to change repmgr_sch
Hey,
yes I did .. and still it wont fail back..
2015-08-13 16:23 GMT+03:00 Jony Vesterman Cohen :
> Hi, did you make the old master follow the new one using repmgr?
>
> It doesn't update itself automatically...
> From the looks of it repmgr thinks you have 2 masters - the old one
> offline and th
-- Forwarded message --
From: Aviel Buskila
Date: 2015-08-13 15:43 GMT+03:00
Subject: Re: [GENERAL] repmgr won't update witness after failover
To: Jony Cohen
Hey,
I have just tried to start the repmgrd on the new standby after I have
fixed it as a standby and still
Hi Aviel,
you can use the 'show cluster' command to see the repmgr state before you
do the 2nd failover - make sure the node1 is indeed marked as replica.
After a failover the Master doesn't automatically attach to the new master
- you need to point him as a slave (standby follow - if possible...)
Hey,
I have set up three nodes of postgresql 9.4 with repmgr in this way:
1. master - node1
2. standby - node2
3. witness - node3
Now I have set up the replication and the witness as it says here:
https://github.com/2ndQuadrant/repmgr/blob/master/FAILOVER.rst
Now when I do 'kill -9 $(pidof postma
I set up repmgr and its working. I confirmed that using:
select * from pg_stat_replication;
select pg_is_in_recovery();
However, on both master and slave there is only one entry
in repmgr_cane.repl_nodes : the master.
Is that expected?
On Mon, Nov 10, 2014 at 4:29 PM, John R Pierce wrote:
On 11/10/2014 4:10 PM, Robin Ranjit Singh Chauhan wrote:
I havent been able to find much about repmgr on postgres 9.3
Is repmgr still a significant value add given the newer replication
features built in?
repmgr is a management tool for setting up and controlling the built in
replication fea
I havent been able to find much about repmgr on postgres 9.3
Is repmgr still a significant value add given the newer replication
features built in?
Thanks.
=R
--
Robin R Chauhan
CEO, Pathway Intelligence Inc
ro...@pathwayi.com
Office: 778-588-6217 Ext. 201
Cell: 604-865-0517
http://pathwayi.com/
> For that matter - is there a reason it has to be an integer? Allowing
> hostnames there would be more friendly. Using integers means someone has to
> maintain a mapping on node IDs to hostnames in a separate place, and then
> that leads to mistakes, like someone thinking the standby node (2) i
On 02/08/11 01:05, Jaime Casanova wrote:
On Wed, Jul 27, 2011 at 7:24 PM, Toby Corkindale
wrote:
On 28/07/11 03:47, Jaime Casanova wrote:
On Wed, Jul 27, 2011 at 4:36 AM, Toby Corkindale
wrote:
So that looks good, but then I try this on the slave:
# repmgr -f /etc/repmgr/validator/repm
On Wed, Jul 27, 2011 at 7:24 PM, Toby Corkindale
wrote:
> On 28/07/11 03:47, Jaime Casanova wrote:
>>
>> On Wed, Jul 27, 2011 at 4:36 AM, Toby Corkindale
>> wrote:
>>>
>>> So that looks good, but then I try this on the slave:
>>> # repmgr -f /etc/repmgr/validator/repmgr.conf \
>>> --verbose sta
On Sat, Jul 30, 2011 at 7:57 AM, Toby Corkindale
wrote:
> Many thanks for clearing that up! I hadn't realised that you could only
> change one of the two options on the fly.
The streaming rep options require a restart also...
--
Simon Riggs http://www.2ndQuadrant.com/
Post
- Original Message -
> wrote:
> > Hi,
> > In the repmgr README, it suggests configuration should include:
> >
> > archive_mode = on
> > archive_command = 'cd .'
> >
> > Could someone explain why we need archive_mode enabled? In my own
> > testing of
> > Pg's streaming replication, I've fou
On Fri, Jul 29, 2011 at 3:12 AM, Toby Corkindale
wrote:
> Hi,
> In the repmgr README, it suggests configuration should include:
>
> archive_mode = on
> archive_command = 'cd .'
>
> Could someone explain why we need archive_mode enabled? In my own testing of
> Pg's streaming replication, I've found
On Friday, July 29, 2011 1:23:55 am Raghavendra wrote:
> On Fri, Jul 29, 2011 at 1:42 PM, Toby Corkindale <
>
> toby.corkind...@strategicdata.com.au> wrote:
> > Hi,
> > In the repmgr README, it suggests configuration should include:
> >
> > archive_mode = on
> > archive_command = 'cd .'
> >
> >
On Fri, Jul 29, 2011 at 1:42 PM, Toby Corkindale <
toby.corkind...@strategicdata.com.au> wrote:
> Hi,
> In the repmgr README, it suggests configuration should include:
>
> archive_mode = on
> archive_command = 'cd .'
>
> Could someone explain why we need archive_mode enabled? In my own testing
> o
Hi,
In the repmgr README, it suggests configuration should include:
archive_mode = on
archive_command = 'cd .'
Could someone explain why we need archive_mode enabled? In my own
testing of Pg's streaming replication, I've found it to work without
this enabled.
Cheers,
Toby
--
Sent via pgsql-
On 28/07/11 03:47, Jaime Casanova wrote:
On Wed, Jul 27, 2011 at 4:36 AM, Toby Corkindale
wrote:
So that looks good, but then I try this on the slave:
# repmgr -f /etc/repmgr/validator/repmgr.conf \
--verbose standby register
can you show the content of /etc/repmgr/validator/repmgr.conf?
On Wed, Jul 27, 2011 at 4:36 AM, Toby Corkindale
wrote:
>
> So that looks good, but then I try this on the slave:
> # repmgr -f /etc/repmgr/validator/repmgr.conf \
> --verbose standby register
>
can you show the content of /etc/repmgr/validator/repmgr.conf?
[...]
>
> I can query the database li
- Original Message -
> On Wed, Jul 27, 2011 at 10:36 AM, Toby Corkindale wrote:
> > Hi,
> > I have repmgr working to some degree on a couple of servers, but am
> > having
> > trouble with the "register" part on the slave.
> >
> > On the master, I run:
> > # repmgr -f /etc/repmgr/validator/r
On Wed, Jul 27, 2011 at 10:36 AM, Toby Corkindale
wrote:
> Hi,
> I have repmgr working to some degree on a couple of servers, but am having
> trouble with the "register" part on the slave.
>
> On the master, I run:
> # repmgr -f /etc/repmgr/validator/repmgr.conf \
> --verbose --force master regis
Hi,
I have repmgr working to some degree on a couple of servers, but am
having trouble with the "register" part on the slave.
On the master, I run:
# repmgr -f /etc/repmgr/validator/repmgr.conf \
--verbose --force master register
Opening configuration file: /etc/repmgr/validator/repmgr.conf
42 matches
Mail list logo
