[GENERAL] BDR not catching up

I'm getting this message repeating on the UDR node that I just added today. Any way to get it start applying? svp2=# select * from bdr.bdr_nodes; node_sysid | node_timeline | node_dboid | node_status | node_name|node_local_dsn |

Re: [GENERAL] BDR concern/issue

On 3 March 2016 at 07:54, cchee-ob wrote: > I queried pg_replication_slots after I removed an BDR node and I noticed a > slot_name that isn't in bdr.bdr_node_slots. And active is 'f' and it has > been retaining bytes. Should I be concerned and is there a way to

[GENERAL] BDR concern/issue

I queried pg_replication_slots after I removed an BDR node and I noticed a slot_name that isn't in bdr.bdr_node_slots. And active is 'f' and it has been retaining bytes. Should I be concerned and is there a way to remove it. I do still have one UDR node which is running

Re: [GENERAL] BDR error trying to replay a invalid statement

On 2 February 2016 at 05:07, cchee-ob wrote: > I noticed that the BDR replication continually trying to replay a ddl > statement that has a syntax error. Is there anything that can be done to > skip this statement or do I need to rebuild the replicated node?

[GENERAL] BDR error trying to replay a invalid statement

I noticed that the BDR replication continually trying to replay a ddl statement that has a syntax error. Is there anything that can be done to skip this statement or do I need to rebuild the replicated node? Here's what I see in the logs: t=2016-02-01 13:02:27 PST d= h= p=21795 a=LOCATION:

Re: [GENERAL] BDR replication on Postgresql 9.5.0

On Mon, Feb 1, 2016 at 12:24 AM, John R Pierce wrote: > On 1/29/2016 3:00 AM, Kaushal Shriyan wrote: > >> >> Do i need to install any BDR specific package to enable it in postgresql >> 9.5 version. While reading >> http://bdr-project.org/docs/0.9.0/install-requirements.html

Re: [GENERAL] BDR replication on Postgresql 9.5.0

On 1/29/2016 3:00 AM, Kaushal Shriyan wrote: Do i need to install any BDR specific package to enable it in postgresql 9.5 version. While reading http://bdr-project.org/docs/0.9.0/install-requirements.html i assumed that it is available in 9.5 version by default without using any patches.

Re: [GENERAL] BDR replication on Postgresql 9.5.0

BDR extension is not available in 9.5. You need to install it separately. - Sachin On 29 Jan 2016 4:31 p.m., "Kaushal Shriyan" wrote: > Hi, > > I am following http://bdr-project.org/docs/stable/index.html to setup BDR > for postgresql version 9.5 as per > >

Re: [GENERAL] BDR replication

On 29 January 2016 at 18:27, Nikhil wrote: > Is there any way to specify priority for replication. or any parameter > which guarantees something about replication (speed at which it replicates, > number of minimum replicas to write). > Not yet. Not in core PostgreSQL

[GENERAL] BDR replication on Postgresql 9.5.0

Hi, I am following http://bdr-project.org/docs/stable/index.html to setup BDR for postgresql version 9.5 as per [root@ip-172-31-1-17 9.5]# cat /etc/redhat-release *Red Hat Enterprise Linux Server release 6.6 (Santiago)* [root@ip-172-31-1-17 9.5]# rpm -qa | grep postgre

Re: [GENERAL] BDR replication

On 1/29/2016 2:27 AM, Nikhil wrote: Is there any way to specify priority for replication. or any parameter which guarantees something about replication (speed at which it replicates, number of minimum replicas to write). Does BDR has a configuration for differentiated services in

[GENERAL] BDR replication

Hello, Is there any way to specify priority for replication. or any parameter which guarantees something about replication (speed at which it replicates, number of minimum replicas to write). Does BDR has a configuration for differentiated services in replication. I want to categorize my data

Re: [GENERAL] BDR with postgres 9.5

On 22 January 2016 at 04:24, Merlin Moncure wrote: > On Wed, Jan 20, 2016 at 12:52 PM, Vik Fearing wrote: > > On 01/20/2016 11:41 AM, Nikhil wrote: > >> Hello All, > >> > >> > >> What is the timeline for BDR with postgres 9.5 released version. > > > >

Re: [GENERAL] BDR with postgres 9.5

On Wed, Jan 20, 2016 at 12:52 PM, Vik Fearing wrote: > On 01/20/2016 11:41 AM, Nikhil wrote: >> Hello All, >> >> >> What is the timeline for BDR with postgres 9.5 released version. > > Currently there are no plans for BDR with 9.5. >

Re: [GENERAL] BDR with postgres 9.5

On 01/20/2016 11:41 AM, Nikhil wrote: > Hello All, > > > What is the timeline for BDR with postgres 9.5 released version. Currently there are no plans for BDR with 9.5. https://github.com/2ndQuadrant/bdr/issues/157#issuecomment-172402366 -- Vik Fearing

[GENERAL] BDR with postgres 9.5

Hello All, What is the timeline for BDR with postgres 9.5 released version. Best Regards, Nikhil

[GENERAL] BDR install broken on Ubuntu 14.04

Hi, I have the same issue. It was working fine a month ago. I wrote a cookbook with chef to install BDR a month ago since then I did not change the cookbook but now I got this error. This seem to be the heart of the issue: Removing obsolete dictionary files: ==> ldev4: * No PostgreSQL

Re: [GENERAL] [BDR] Best practice to automatically abort a DDL operation when one node is down

What is the best practice to make sure the DDL operation will fail, possibly after a timeout, if one of the node is down? statement_timeout Ok. Thank-you for pointing this. I have just tried it, and this work great even for nodes that are not properly power off (plug removed).

Re: [GENERAL] [BDR] Best practice to automatically abort a DDL operation when one node is down

On 13 January 2016 at 21:45, Sylvain MARECHAL wrote: > The problem is that the (1) DDL request will wait indefinitely, meaning > all transactions will continue to fail until the DDL operation is manually > aborted (for example, doing CTRL C in psql to abort the

Re: [GENERAL] BDR: cascading setup

On 11 January 2016 at 18:55, Oleksii Kliukin wrote: > We are evaluating BDR for a multi-master cross-datacenter replication, > with 2 masters actually communicating across datacenter, supplemented by a > local in-datacenter replicas to provide HA. > This is strongly

[GENERAL] [BDR] Best practice to automatically abort a DDL operation when one node is down

Hello all, I am using BDR with two nodes 1 and 2. If I issue a DDL operation in node 1 when node 2 is down, for example: CREATE TABLE test (i int PRIMARY KEY); (1) all other transactions fail with the following error: Database is locked against DDL operations The problem is that the (1)

Re: [GENERAL] BDR install broken on Ubuntu 14.04

On 13-01-16 17:48, LOUBRADOU, Rémy wrote: Hi, I have the same issue. It was working fine a month ago. I wrote a cookbook with chef to install BDR a month ago since then I did not change the cookbook but now I got this error. This seem to be the heart of the issue: Removing obsolete

[GENERAL] BDR: cascading setup

Hi, We are evaluating BDR for a multi-master cross-datacenter replication, with 2 masters actually communicating across datacenter, supplemented by a local in-datacenter replicas to provide HA. Basically, something like M <——> M || S S I could run all nodes as

Re: [GENERAL] BDR and TX obeyance

On 5 January 2016 at 04:09, Riley Berton wrote: > > The conflict on the "thingy" table has resulted in node2 winning based > on last_update wins default resolution. However, both inserts have > applied. My expectation is that the entire TX applies or does not > apply.

Re: [GENERAL] BDR and TX obeyance

On 4 January 2016 at 20:09, Riley Berton wrote: > The conflict on the "thingy" table has resulted in node2 winning based > on last_update wins default resolution. However, both inserts have > applied. My expectation is that the entire TX applies or does not > apply.

Re: [GENERAL] BDR and TX obeyance

Craig Ringer writes: > On 5 January 2016 at 04:09, Riley Berton wrote: > >> >> The conflict on the "thingy" table has resulted in node2 winning based >> on last_update wins default resolution. However, both inserts have >> applied. My expectation

[GENERAL] BDR install broken on Ubuntu 14.04

Hi, I'm installing BDR on a ubuntu 14.04 (Trusty) machine. I can reproduce this error. It happens locally with a new VM and on Digital ocean. The error is: /var/lib/dpkg/info/postgresql-bdr-9.4.postinst: 95: /var/lib/dpkg/info/postgresql-bdr-9.4.postinst: db_stop: not found How can I fix

Re: [GENERAL] BDR and TX obeyance

Em 05/01/2016 11:42, Riley Berton escreveu: Edson Richter writes: BTW, I'm also looking for a "synchronous multi-master" solution... If you find one, please share :-) The only solution I've found so far is a middleware that is close, the C-Jdbc/Sequoia, which seems

Re: [GENERAL] BDR and TX obeyance

Edson Richter writes: > BTW, I'm also looking for a "synchronous multi-master" solution... If > you find one, please share :-) > The only solution I've found so far is a middleware that is close, the > C-Jdbc/Sequoia, which seems not being actively maintained for a

[GENERAL] BDR and TX obeyance

I have been experimenting with BDR and have a question about how BDR interacts with transactions. bdrdemo=# create table thingy (id INT, value TEXT, PRIMARY KEY(id)); CREATE TABLE bdrdemo=# create table tx_log(id INT, msg TEXT, PRIMARY KEY(id)); CREATE TABLE bdrdemo=# insert into thingy (id,

Re: [GENERAL] BDR and TX obeyance

I think this is the nature of "async multi master"... IMHO, It would be necessary to be "sync multi master" (with two-phase commit?) to get the behavior you expect. Atenciosamente, Edson Carlos Ericksson Richter Em 04/01/2016 18:09, Riley Berton escreveu: I have been experimenting with BDR

Re: [GENERAL] BDR and TX obeyance

BTW, I'm also looking for a "synchronous multi-master" solution... If you find one, please share :-) The only solution I've found so far is a middleware that is close, the C-Jdbc/Sequoia, which seems not being actively maintained for a while now. Regards, Edson Atenciosamente, Edson Carlos

[GENERAL] BDR and synchronous replication

Hello, i am experimenting BDR project. As BDR does asynchronous replication, i have a query regarding bdr.synchronous_commit=on option. Will aforementioned configuration in postgresql.conf makes the replication synchronous? Does this require any other setting? any side effect for using this

Re: [GENERAL] BDR and synchronous replication

On 26 December 2015 at 19:29, Nikhil wrote: > Hello, > > i am experimenting BDR project. As BDR does asynchronous replication, i > have a query regarding bdr.synchronous_commit=on option. > > Will aforementioned configuration in postgresql.conf makes the replication >

Re: [GENERAL] BDR error while adding 3rd node to cluster

Thanks you very much Craig for this help. This is the error due to dns entry I pointed pg3 on two different IP. I regret for wasting your precious time that I could not pick such a small thing. thanks again. On Thu, Dec 24, 2015 at 3:55 PM, Craig Ringer wrote: > > > On

Re: [GENERAL] BDR error while adding 3rd node to cluster

On 22 December 2015 at 17:00, Amit Bondwal wrote: > I remove all the bdr packages and reinstall it and setup again the BDR > cluster, still facing the same issue on 3rd node. > At this point I'd really need to see the steps taken, in detail, to get to that point from a

Re: [GENERAL] BDR error while adding 3rd node to cluster

Hi Craig, I remove all the bdr packages and reinstall it and setup again the BDR cluster, still facing the same issue on 3rd node. On Tue, Dec 22, 2015 at 10:58 AM, Amit Bondwal wrote: > > On Tue, Dec 22, 2015 at 10:05 AM, Craig Ringer > wrote: >

Re: [GENERAL] BDR error while adding 3rd node to cluster

On 21 December 2015 at 22:57, Amit Bondwal wrote: > Hi Everyone, > > I am trying to setup three node bdr cluster, I am following the quick > start guide, > It is working well between first and 2nd node, but When I try to add 3rd > node, it give the below error. > >

Re: [GENERAL] BDR error while adding 3rd node to cluster

On Tue, Dec 22, 2015 at 10:05 AM, Craig Ringer wrote: > select * from bdr.bdr_connections; > Hi Craig, Thanks for your reply, These commands shows nothing on 3rd node. *on node3:-*hakuna=# select * from bdr.bdr_nodes; node_sysid | node_timeline | node_dboid |

[GENERAL] BDR error while adding 3rd node to cluster

Hi Everyone, I am trying to setup three node bdr cluster, I am following the quick start guide, It is working well between first and 2nd node, but When I try to add 3rd node, it give the below error. hakuna=# SELECT bdr.bdr_group_join( local_node_name := 'node3', node_external_dsn :=

[GENERAL] BDR

Hi @ll, I would like to play with BDR, can i use my 9.5 / 9.6 installation (first attempt fails) or do i have to use 9.4 stable? Regards, Andreas -- Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect. (Linus Torvalds)

Re: [GENERAL] BDR

On 12/15/2015 12:01 AM, Andreas Kretschmer wrote: I would like to play with BDR, can i use my 9.5 / 9.6 installation (first attempt fails) or do i have to use 9.4 stable? 9.5 is a in-development version, 9.6 doesn't even exist, why would you want to use anything OTHER than the stable and

Re: [GENERAL] BDR

John R Pierce wrote: > On 12/15/2015 12:01 AM, Andreas Kretschmer wrote: >> I would like to play with BDR, can i use my 9.5 / 9.6 installation >> (first attempt fails) or do i have to use 9.4 stable? > > 9.5 is a in-development version, 9.6 doesn't even exist, why would you

Re: [GENERAL] BDR

On 15 December 2015 at 16:49, Andreas Kretschmer wrote: > BDR is currently an addon for 9.4, I don't believe its available for 9.5 > > yet. > > apparently, thx for the answer. Correct, there's no BDR for 9.5. There's a pretty good chance we'll skip 9.5 entirely and

Re: [GENERAL] BDR

Craig Ringer wrote: > On 15 December 2015 at 16:49, Andreas Kretschmer > wrote: > > > > BDR is currently an addon for 9.4, I don't believe its available for 9.5 > > yet. > > apparently, thx for the answer. > > > Correct, there's

Re: [GENERAL] bdr manual cleanup required

I really couldn't say with the available information. Can you set provide a step-by-step process by which you set up these nodes? ​

Re: [GENERAL] bdr manual cleanup required

Le 09/12/2015 05:18, Craig Ringer a écrit : Are you adding more than one node at once? BDR isn't currently smart enough to handle that. Make sure to wait until one node is fully synced up before adding another. ​ In other words, one shall not attemp to add a new node if the other nodes are

Re: [GENERAL] BDR: ALTER statement hanging

in any log messages and the replication was working as it should. -Selim From: Craig Ringer [cr...@2ndquadrant.com] Sent: Sunday, December 06, 2015 7:05 PM To: Selim Tuvi Cc: Sylvain MARECHAL; pgsql-general@postgresql.org Subject: Re: [GENERAL] BDR: ALTER statement

Re: [GENERAL] bdr manual cleanup required

ode to the third node. -Selim From: Sylvain Marechal [marechal.sylva...@gmail.com] Sent: Sunday, December 06, 2015 4:23 AM To: Selim Tuvi Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] bdr manual cleanup required Did you try this : https://github.com/2ndQuadrant/bdr/issu

Re: [GENERAL] bdr manual cleanup required

chal.sylva...@gmail.com] *Sent:* Sunday, December 06, 2015 4:23 AM *To:* Selim Tuvi *Cc:* pgsql-general@postgresql.org *Subject:* Re: [GENERAL] bdr manual cleanup required Did you try this : https://github.com/2ndQuadrant/bdr/issues/127 : <<< |BEGIN; SET LOC

Re: [GENERAL] bdr manual cleanup required

Are you adding more than one node at once? BDR isn't currently smart enough to handle that. Make sure to wait until one node is fully synced up before adding another. ​

Re: [GENERAL] bdr manual cleanup required

Did you try this : https://github.com/2ndQuadrant/bdr/issues/127 : <<< BEGIN; SET LOCAL bdr.skip_ddl_locking = on; SET LOCAL bdr.permit_unsafe_ddl_commands = on; SET LOCAL bdr.skip_ddl_replication = on; SECURITY LABEL FOR bdr ON DATABASE mydb IS NULL; DELETE FROM bdr.bdr_connections; DELETE FROM

Re: [GENERAL] BDR: ALTER statement hanging

​If you're not sure what's going on on a node, look at its logs. The background worker API and PostgreSQL's lack of autonomous transactions makes it quite challenging for BDR workers to capture logs and expose them to users at the SQL level. So always, if in doubt, examine the log files.

Re: [GENERAL] BDR: ALTER statement hanging

From: pgsql-general-ow...@postgresql.org [pgsql-general-ow...@postgresql.org] on behalf of Andreas Kretschmer [akretsch...@spamfence.net] Sent: Thursday, December 03, 2015 10:49 PM To: pgsql-general@postgresql.org Subject: Re: [GENERAL] BDR: ALTER statement

[GENERAL] bdr manual cleanup required

I am trying to repair a broken bdr cluster setup and so far everything I tried failed. Under the original node that ran bdr.bdr_group_create I am getting the following error: 2015-12-04 19:34:29.063 UTC,,,22991,,5661eac4.59cf,1,,2015-12-04 19:34:28 UTC,3/0,0,ERROR,55000,"previous init failed,

Re: [GENERAL] BDR: ALTER statement hanging

ow...@postgresql.org] on behalf of Andreas Kretschmer [andr...@a-kretschmer.de] Sent: Friday, December 04, 2015 9:59 AM To: pgsql-general@postgresql.org Subject: Re: [GENERAL] BDR: ALTER statement hanging > Selim Tuvi <st...@ilm.com> hat am 4. Dezember 2015 um 18:46 geschrieben: > > > Y

Re: [GENERAL] BDR: ALTER statement hanging

-general@postgresql.org Subject: Re: [GENERAL] BDR: ALTER statement hanging Le 04/12/2015 18:59, Andreas Kretschmer a écrit : > > > I think, the state 'i' is the main reason for your problem, because of: "i- > Joining: The node is doing initial slot creation or an initial dump and

Re: [GENERAL] BDR: ALTER statement hanging

Le 04/12/2015 18:59, Andreas Kretschmer a écrit : I think, the state 'i' is the main reason for your problem, because of: "i- Joining: The node is doing initial slot creation or an initial dump and load". But i can't tell you why this nodes are in this state. Regards, Andreas Did-you

Re: [GENERAL] BDR: ALTER statement hanging

> Selim Tuvi hat am 4. Dezember 2015 um 18:46 geschrieben: > > > Yes they seem to be active: > > deliver=# select * from pg_replication_slots; > slot_name | plugin | slot_type | datoid | > database | active | xmin | catalog_xmin | restart_lsn >

Re: [GENERAL] BDR: ALTER statement hanging

Selim Tuvi wrote: > Hi, I am running a three node BDR cluster. BDR version is 0.9.3. Postgres > version is 9.4.5. > > With 0.9.2, I used to be able to issue ALTER statements using psql and it > would > go through. This time it is just hanging. The statement is this: for

[GENERAL] BDR: ALTER statement hanging

Hi, I am running a three node BDR cluster. BDR version is 0.9.3. Postgres version is 9.4.5. With 0.9.2, I used to be able to issue ALTER statements using psql and it would go through. This time it is just hanging. The statement is this: alter table pts alter column shot drop not null; I also

Re: [GENERAL] BDR and Backup and Recovery

On 19 November 2015 at 00:54, Will McCormick wrote: > The below is from the 0.9.3 BDR documentation: > > "Because logical replication is only supported in streaming mode (rather > than WAL archiving) it isn't suitable for point-in-time recovery. Logical > replication may

Re: [GENERAL] BDR and Backup and Recovery

On 18 November 2015 at 23:46, Will McCormick wrote: > What viable options exist for Backup & Recovery in a BDR environment? From > the reading I have done PITR recovery is not an option with BDR. It's > important to preface this that I have almost no exposure to postgres

Re: [GENERAL] BDR and Backup and Recovery

On 11/18/2015 08:54 AM, Will McCormick wrote: Re-sending to group as well Jim :D Regarding testing backups, Well said Jim. Thanks for taking the time to respond. I will test regularly whatever we decide to put in place. The below is from the 0.9.3 BDR documentation: "Because logical

Re: [GENERAL] BDR and Backup and Recovery

On 11/18/15 10:53 AM, Will McCormick wrote: Regarding testing backups, Well said Jim. Thanks for taking the time to respond. I will test regularly whatever we decide to put in place. The below is from the 0.9.3 BDR documentation: "Because logical replication is only supported in streaming mode

Re: [GENERAL] BDR and Backup and Recovery

Re-sending to group as well Jim :D Regarding testing backups, Well said Jim. Thanks for taking the time to respond. I will test regularly whatever we decide to put in place. The below is from the 0.9.3 BDR documentation: "Because logical replication is only supported in streaming mode (rather

Re: [GENERAL] BDR and Backup and Recovery

On 11/18/2015 09:31 AM, Will McCormick wrote: Ccing list Thanks Adrian. I think I have it Lets say we have 2 nodes: Node A Node B GOOD Application Writes only occurring against Node A 1) Node A Base Backup taken 2) User Error occurs that replicates Can restore and Recover Node A to PITR

[GENERAL] BDR and Backup and Recovery

What viable options exist for Backup & Recovery in a BDR environment? From the reading I have done PITR recovery is not an option with BDR. It's important to preface this that I have almost no exposure to postgres backup and recovery. Is PITR not an option with BDR? If a user fat fingers

Re: [GENERAL] BDR and Backup and Recovery

On 11/18/15 9:46 AM, Will McCormick wrote: What viable options exist for Backup & Recovery in a BDR environment? From the reading I have done PITR recovery is not an option with BDR. It's important to preface this that I have almost no exposure to postgres backup and recovery. Is PITR not an

Re: [GENERAL] bdr appears to be trying to replicate to itself

Cj B wrote: > I noticed a very strange issue starting about 20 days ago and my pg_xlog has > just been filling up since then. For reference, this was also asked on github, and answered there. See https://github.com/2ndQuadrant/bdr/issues/143 -- Álvaro Herrera

Re: [GENERAL] bdr appears to be trying to replicate to itself

Hi, Yes, I posted on github because I wasn’t sure where to post. And the reason I’m posting here is because I’m not clear about the answer "Drop the slot bdr_16385_6188730679935789649_1_16385__ on the first host.” Do this just mean to select

[GENERAL] bdr appears to be trying to replicate to itself

I noticed a very strange issue starting about 20 days ago and my pg_xlog has just been filling up since then. ``` HOST A: postgres=# select * from pg_replication_slots; slot_name| plugin | slot_type | datoid | database | active | xmin | catalog_xmin |

Re: [GENERAL] bdr appears to be trying to replicate to itself

> On 17 November 2015 at 00:33, Cj B > wrote: > > This doesn't explain how the system got into this state. For that it'd really > be necessary to see the steps taken during setup. BDR tries to protect > against attempts to

Re: [GENERAL] bdr appears to be trying to replicate to itself

On 17 November 2015 at 00:33, Cj B wrote: > select pg_drop_replication_slot(‘bdr_16385_6188730679935789649_1_16385__’) > Correct. > What impact will this have? If the slot is unused, it'll allow the WAL that's being held by the slot to be removed. It'll also unpin the

[GENERAL] BDR - Remove & Join

I have a script which is meant to remove a node from bdr replication. Two nodes in replication node A and node B. The script does the following. 1. On node A - SELECT bdr.bdr_part_by_node_names(ARRAY['node B']); 2. On node A -Checks that the node_status is marked as 'k' in bdr.bdr_nodes 3. I

Re: [GENERAL] BDR - Remove & Join

On 10 November 2015 at 05:10, Will McCormick wrote: > I then run a script which I used to setup replication before removal. The > problem I encounter is node B after join in bdr.bdr_nodes is stuck in status > 'c'. [snip] > We are using the following version of bdr:

[GENERAL] BDR: SSL error: bad write retry

BDR-0.9.3 and PG-9.4.4 on Ubuntu 14.04 Two nodes, BDR replication. Cluster is newly created, no nodes have been removed from it. Making/deleting small tables works well across the cluster. Now I'm trying to pg_restore a larger database from another system (pg_dump output file is 3.1 GB

Re: [GENERAL] BDR: name conflict when joining a rebuilt node

Still having issues with this with BDR-0.9.3 This is how I join a new node to the cluster: su - postgres psql pgmirror -- fire up BDR extensions CREATE EXTENSION btree_gist; CREATE EXTENSION bdr; -- join BDR group via an existing node there SELECT

Re: [GENERAL] BDR: SSL error: bad write retry

Nevermind, this was fixed with: ssl_renegotiation_limit = 0 -- Florin Andrei http://florin.myip.org/ -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] BDR-Plugin make install on RHEL7.1

On Thu, 2015-10-29 at 08:33 -0400, Will McCormick wrote: > Trying to get the bdr-plugin to install make install on RHEL7.1. Having some > issues with make of the plugin. > > > > # make -j4 -s all make -s install > make: *** No rule to make target `make'. Stop. > make: *** Waiting for

[GENERAL] BDR-Plugin make install on RHEL7.1

Trying to get the bdr-plugin to install make install on RHEL7.1. Having some issues with make of the plugin. Here is what I have run verbatim and the error is at the very bottom. Any help is appreciated. Please let me know if there is another forum I should be posting this to. I'm assuming I'm

[GENERAL] bdr-plugin packages repo not updated to 0.9.3?

http://packages.2ndquadrant.com/bdr/apt/pool/main/b/bdr-plugin/ Looks like the repo has not caught up to the latest 0.9.3 release. Would it be possible to push updated packages to the repo, please? It would be a great help with testing BDR. Thanks, -- Florin Andrei http://florin.myip.org/

[GENERAL] BDR: name conflict when joining a rebuilt node

Let's say node pg12 in a cluster needs to be removed because it has serious problems. I remove it by running this command on another node in the cluster: SELECT bdr.bdr_part_by_node_names('{pg12}'); On pg12, I run this: BEGIN; SET LOCAL bdr.permit_unsafe_ddl_commands = true; SET LOCAL

Re: [GENERAL] BDR: name conflict when joining a rebuilt node

On 30 October 2015 at 08:24, Florin Andrei wrote: > The problem is, bdr_node_join_wait_for_ready() never returns, it just waits > forever. If I go on pg11 and run SELECT * FROM bdr.bdr_nodes, I see pg12 > listed twice, with node_status k and i, respectively. On pg11 I see

Re: [GENERAL] BDR - DDL Locking

Hey Craig thank you very much for your response. > When you say you "attempted to" - what was the outcome? I tried a truncate without the cascade option. After that I tried it with the cascade option. The session just hanged indefinitely at that point. There was no rollback and I was testing on

Re: [GENERAL] BDR - DDL Locking

Will, I saw after replying that there's more detail I missed in your mail, so please see the more detailed reply inline below. On 20 October 2015 at 23:31, Will McCormick wrote: > First time user here and new to PostgreSQL and BDR so I hope I have the > right place. You

Re: [GENERAL] BDR - DDL Locking

What's the *exact* BDR version? When you say you "attempted to" - what was the outcome? Presumably an ERROR from the TRUNCATE, right? That would roll back the transaction, and in the process abort the DDL lock acquisition attempt. Are you sure replication was working normally prior to this

[GENERAL] BDR: pg_stat_bdr: cache lookup failed

Hi we are currently testing BDR 0.9.2 and I set up a two node cluster. From one node I can run: select * from bdr.pg_stat_bdr and it gives me the rows fine but on the other node I get the following error: ERROR: cache lookup failed for replication identifier id: 4 Any idea why? The server

Re: [GENERAL] BDR workers exiting?

On 10/12/15 10:14 AM, Jim Nasby wrote: On 10/12/15 9:37 AM, Steve Pribyl wrote: I am loading up a 60G database into BDR database and these "ERRORS" are in my logs. Is not normal behavior or is something going bad. 2015-10-12 09:28:59.389 CDT,,,30371,,561bc17d.76a3,1,,2015-10-12 09:19:41

Re: [GENERAL] BDR workers exiting?

he change callback, associated LSN 2/FD250E48""bdr (6204748238611542317,1,16494,):receive" Steve Pribyl Sr. Systems Engineer steve.pri...@akunacapital.com Desk: 312-994-4646 From: Andres Freund <and...@anarazel.de> Sent: Monday, October 12, 2015 11:0

Re: [GENERAL] BDR workers exiting?

On 2015-10-12 14:37:07 +, Steve Pribyl wrote: > I am loading up a 60G database into BDR database and these "ERRORS" are in my > logs. Is not normal behavior or is something going bad. > > 2015-10-12 09:28:59.389 CDT,,,30371,,561bc17d.76a3,1,,2015-10-12 09:19:41 >

[GENERAL] BDR workers exiting?

I am loading up a 60G database into BDR database and these "ERRORS" are in my logs. Is not normal behavior or is something going bad. 2015-10-12 09:28:59.389 CDT,,,30371,,561bc17d.76a3,1,,2015-10-12 09:19:41 CDT,5/0,0,ERROR,XX000,"data stream ended","bdr

Re: [GENERAL] BDR workers exiting?

On 10/12/15 9:37 AM, Steve Pribyl wrote: I am loading up a 60G database into BDR database and these "ERRORS" are in my logs. Is not normal behavior or is something going bad. 2015-10-12 09:28:59.389 CDT,,,30371,,561bc17d.76a3,1,,2015-10-12 09:19:41 CDT,5/0,0,ERROR,XX000,"data stream

Re: [GENERAL] BDR workers exiting?

bdr. Glad to have a work around but would like to get to understand the failure. Steve Pribyl From: Steve Pribyl Sent: Monday, October 12, 2015 11:19 AM To: Andres Freund Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] BDR workers exiting?

Re: [GENERAL] BDR: no free replication state could be found

On 10 October 2015 at 02:53, Selim Tuvi wrote: > node: deliver_sing (the problem node): > > postgres=# SELECT * FROM pg_catalog.pg_replication_identifier; > riident | riname > -+ >1 |

Re: [GENERAL] BDR workers exiting?

BDR is currently memory-limited for extremely large transactions. At a guess, I'd say one of your big tables is large enough that the logical decoding facility BDR uses can't keep track of the transaction properly. There's no hard limit, it depends on details of the transaction and a number of

Re: [GENERAL] BDR: no free replication state could be found

On 9 October 2015 at 06:54, Selim Tuvi wrote: > Hi I am testing BDR functionality with Postgres 9.4. I had went through the > bdrdemo example with a 3 node cluster and then tried to set up my own db. > > My "max_replication_slots" is set to 6. After getting removing the bdrdemo >

Re: [GENERAL] BDR: no free replication state could be found

: Craig Ringer [cr...@2ndquadrant.com] Sent: Thursday, October 08, 2015 11:05 PM To: Selim Tuvi Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] BDR: no free replication state could be found On 9 October 2015 at 06:54, Selim Tuvi <st...@ilm.com> wrote: > Hi I am testing BDR func

[GENERAL] BDR: no free replication state could be found

Hi I am testing BDR functionality with Postgres 9.4. I had went through the bdrdemo example with a 3 node cluster and then tried to set up my own db. My "max_replication_slots" is set to 6. After getting removing the bdrdemo db I am having trouble starting up the postgres instance unless I

Re: [GENERAL] BDR Rejoin of failed node, hangs.

ct: Re: [GENERAL] BDR Rejoin of failed node, hangs. On 5 October 2015 at 20:58, Steve Pribyl <spri...@akunacapital.com> wrote: > Clean up node 1. >select bdr.bdr_part_by_node_names('{node2}'); >delete from bdr.bdr_nodes where node_status='k'; You need to delete the bdr.bdr_

<    1   2   3   4   >