gt;
Cc: PostgreSql-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] BDR replication port
That's weird. Another idea: Do changes on that server get replicated to the
other servers? I'm not sure if incomming connections are used to receive WAL or
to send it.
Regards,
Alvaro Ag
017 3:23 PM
To: Zhu, Joshua <j...@thalesesec.net>
Cc: PostgreSql-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] BDR replication port
Just a guess: How did you blocked the port? Depending on that, you could be
blocking only new connections, but connections already est
greSql-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] BDR replication port
Just a guess: How did you blocked the port? Depending on that, you could be
blocking only new connections, but connections already established would
continue to transmit data; remember BDR only rec
.
Oficina: (+51-1) 3377813 | RPM: #034252 / (+51) 995540103 | RPC: (+51)
954183248
Website: www.ocs.pe
- Original Message -
From: "Zhu, Joshua" <j...@vormetric.com>
To: "PostgreSql-general" <pgsql-general@postgresql.org>
Sent: Friday, 25 August, 2017 16:49:44
Su
Hi, I am experimenting how network configuration impacts BDR replication, ran
into something that I can't explain, and wonder if someone can shed light.
Here it goes:
With a four node BDR group configured and running (all using default port
5432), I purposely blocked port 5432 on one of the
> However if I perform any INSERT, UPDATE or DELETE operations on
> DB2 and these changes propagate over to DB1 via BDR I do not see DB1 firing
> any triggers. Is this intended behavior?
Yes.
> My current understanding is that
> BDR is unable to invoke Postgres triggers as it operates on the
>
> Alvaro Aguayo
> Jefe de Operaciones
> Open Comb Systems E.I.R.L.
>
> Oficina: (+51-1) 3377813 | RPM: #034252 / (+51) 995540103 | RPC: (+51)
> 954183248
> Website: www.ocs.pe
>
> - Original Message -
> From: "jamesadams89" <jamesadam...@hotm
www.ocs.pe
- Original Message -
From: "jamesadams89" <jamesadam...@hotmail.com>
To: "PostgreSql-general" <pgsql-general@postgresql.org>
Sent: Wednesday, 26 April, 2017 07:48:03
Subject: [GENERAL] BDR replication and table triggers
Hi,
I have some questions rega
Hi,
I have some questions regarding how BDR interacts with triggers.
I have two databases that are both joined to the same BDR group and
correctly replicating between one another sharing a table created as:
create table testtable(
key varchar(16) NOT NULL PRIMARY KEY,
data
On interface down:
--
<10.102.31.213(27599)postgres13082016-04-19 06:31:36
GMTprocess_journal%LOG: terminating walsender process due to replication
timeout
Once interface is brought back
425906 <12692016-04-19 08:32:58 GMT%LOG: starting
2016-04-19 6:51 GMT+02:00 Nikhil :
> Hello,
>
> I have a 2 node BDR group and replication is happening properly. if i
> bring down one of the node's interface, after sometime the replication
> slots are becoming inactive (pg_replication_slots view). Then if i bring
> back
Hello,
What do you see on each node's log after enablibg interfaces?
Regards,
Alvaro Aguayo
Jefe de Operaciones
Open Comb Systems E.I.R.L.
Oficina: (+51-1) 3377813 | RPM: #034252 / (+51) 995540103 | RPC: (+51)
954183248
Website: www.ocs.pe
Sent from my Sony Xperia™ smartphone
Nikhil
Hello,
I have a 2 node BDR group and replication is happening properly. if i bring
down one of the node's interface, after sometime the replication slots are
becoming inactive (pg_replication_slots view). Then if i bring back
interface slots are not turning active automatically and replication
"volga629" <volga...@skillsearch.ca>
Cc: "pgsql-general" <pgsql-general@postgresql.org>, "John R Pierce"
<pie...@hogranch.com>
Sent: Thursday, 31 March, 2016 02:41:17
Subject: Re: [GENERAL] bdr replication
We are overlaping mails :P
What
On 3/30/2016 10:41 PM, Alvaro Aguayo Garcia-Rada wrote:
What I don't understand is the need of a shared storage in this case. It would
be a lot better to have the data folder inside each server virtual disk to
avoid troubles with the shared storage; I really see no reason for such
ohn R Pierce"
<pie...@hogranch.com>
Sent: Thursday, 31 March, 2016 12:28:09 AM
Subject: Re: [GENERAL] bdr replication
Hello Alvaro,
We running BDR where each PostgreSQL vm is a master and shared storage only on
hypervisor level. All vm leave with own virtual disk. Right now we have
pie...@hogranch.com>
Sent: Thursday, 31 March, 2016 02:19:42
Subject: Re: [GENERAL] bdr replication
What's the purpose of such configuration? Doesn't makes sense for me. The only
reasonable case where you would want to put the data folder on a shared storage
is for usage with warm standby, wh
resql.org>
Sent: Wednesday, 30 March, 2016 10:57:13 PM
Subject: Re: [GENERAL] bdr replication
In my case only virtual hosts are use share storage (feed from glusterfs), but
actual virtual machines have own separate disks and all PostgreSQL run on
separate data directories.
volga629
--
a>
To: "John R Pierce" <pie...@hogranch.com>
Cc: "pgsql-general" <pgsql-general@postgresql.org>
Sent: Thursday, 31 March, 2016 00:57:13
Subject: Re: [GENERAL] bdr replication
In my case only virtual hosts are use share storage (feed from glusterfs), but
general@postgresql.org>
Sent: Thursday, 31 March, 2016 00:34:55
Subject: Re: [GENERAL] bdr replication
On 3/30/2016 8:09 PM, Slava Bendersky wrote:
> Is any share storage technology recommended for PostgreSQL in virtual
> environment ?
> Ok what I will do is going take backups, s
;
To: "volga629" <volga...@skillsearch.ca>
Cc: "pgsql-general" <pgsql-general@postgresql.org>
Sent: Wednesday, 30 March, 2016 23:57:28
Subject: Re: [GENERAL] bdr replication
On 31 March 2016 at 10:43, Slava Bendersky < volga...@skillsearch.ca > wrote:
H
On 31 March 2016 at 10:43, Slava Bendersky wrote:
> Hello Craig,
> The current setup is two server which run libvirt and for storage which
> run glusterfs (storage server feed two virtual servers). Right now is no
> fencing in place. Each of the nodes have one
dquadrant.com>
To: "volga629" <volga...@skillsearch.ca>
Cc: "pgsql-general" <pgsql-general@postgresql.org>
Sent: Wednesday, 30 March, 2016 23:20:49
Subject: Re: [GENERAL] bdr replication
On 31 March 2016 at 09:38, Slava Bendersky < volga...@skillsearch.ca > wrote
On 31 March 2016 at 09:38, Slava Bendersky wrote:
> Hello Everyone,
> I am looking for suggestion how to recover bdr replication.
> The short story we have 2 virtual nodes with share storage.
>
Can you describe the "shared storage" setup in more detail?
In general,
Hello Everyone,
I am looking for suggestion how to recover bdr replication.
The short story we have 2 virtual nodes with share storage. Share storage lost
power and after I brought all online bdr doesn't work properly.
Here are some log
2016-03-30 20:47:26 EDT
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
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.
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
>
>
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
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
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
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
Craig,
Your response was very helpful, thank you.
I was looking at some of the standard bits in Postgres like
txid_current_snapshot() and txid_snapshot_xmin(). Can the results from
txid_snapshot_xmin be used with pg_get_transaction_committime() to get the
latency?
Thanks again,
Steve Boyle
Steve,
The relevant change was made during the commit of logical decoding to
PostgreSQL 9.4, where the field of interest was renamed from 'xmin' to
'catalog_xmin'. It's around then that pg_stat_logical_decoding was renamed
to pg_replication_slots too.
To get lag in bytes, use:
SELECT slot_name,
I'm trying to follow the BDR monitoring docs:
https://wiki.postgresql.org/wiki/BDR_Monitoring
My postgres version string is (its from the 2nd Quadrant repo):
PostgreSQL 9.4.0 on x86_64-unknown-linux-gnu, compiled by gcc (Ubuntu/Linaro
4.6.3-1ubuntu5) 4.6.3, 64-bit
My BDR plugin is version
35 matches
Mail list logo