Hi. I've had experience with both BDR & pglogical. For each replication slot,
postgres saves a LSN which points to the last xlog entry read by the client.
When a client does not reads xlog, for example, if it cannot connect to the
server, then the distance between such LSN(pg_replication_slots.r
252 / (+51) 995540103 | RPC: (+51)
954183248
Website: www.ocs.pe
- Original Message -
From: "Zhu, Joshua"
To: "Alvaro Aguayo Garcia-Rada"
Cc: "PostgreSql-general"
Sent: Friday, 25 August, 2017 18:35:21
Subject: RE: [GENERAL] BDR replication port
Thought about t
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 reconnects when connection is lost.
Alvaro Aguayo
Jefe de Operaciones
Open Comb Systems E.I.R.L.
Ofic
Hi. I currently have a two-server BDR replication setup. Apart from the two
master nodes, I have another two servers which I want to have read only
replication for some tables only.
I first had to deal with some trouble regarding CREATE EXTENSION being
replicated by BDR, and that causing the sc
Hi.
It's not like BDR is unable to replicate triggers across the cluster: BDR is
not intended to do so.
BDR replicates everything that happens inside a transaction; that includes both
SQL run directly from the application, as well as changes made by triggers and
extensions. As the changes are
www.ocs.pe
- Original Message -
From: "Sachin Srivastava"
To: "Alvaro Aguayo Garcia-Rada"
Cc: "pgsql-general@postgresql.org >> PG-General Mailing List"
Sent: Sunday, 19 February, 2017 1:03:09 AM
Subject: Re: [GENERAL] No space left on device
With correct
Cleanup some space on that device. Maybe your "pg_log" folder has some space to
free. If that doesn't helps, you may need to forcefully add more space. There's
not really much alternatives there.
Alvaro Aguayo
Jefe de Operaciones
Open Comb Systems E.I.R.L.
Oficina: (+51-1) 3377813 | RPM: #03425
Hi.
I had to implement something similar some time ago. Basically, a group of
database servers (postgres) geographically distributed, with each one having a
group of servers in each datacenter, and each server preferring the nearest
database server, but allowing connections to a further one if
Hi. If the explanation given on one of the stackoverflow responses is right,
then there's no current solution for that.
But I would go a little bit further: is it a real problem? I mean, even being a
bug, it does not disrupts the basic behaviour of the sequences: that each
successive call to ne
Hello. BDR works on a per-database basis, so there's nothing like what you are
looking for. However, if you initialize a BDR custer with bdr_init_copy, you
will get all existing databases added to replication. Then, as part of the
creation of new databases, you can use bdr_group_join function, w
Block based replication is the replication mechanism postgres incorporates
natively. It's, in brief, sending all the file-level changes to all the slaves,
so the data folder is always the same. It's like having a replicated folder,
not including logs and some other things.
The disadvantage of b
On Wed, Apr 27, 2016 at 11:56 AM, Craig Ringer
wrote:
> On 27 April 2016 at 23:43, Alvaro Aguayo Garcia-Rada <
> aagu...@opensysperu.com> wrote:
>
>> Based on my experience, I can say BDR does not performs pre-DDL checks.
>> For example, if you try to CREATE TABLE with
Based on my experience, I can say BDR does not performs pre-DDL checks. For
example, if you try to CREATE TABLE with the name of an existing table, BDR
will acquire lock anyway, and then will fail when executing the DDL statement
on the first node, because the table already exists.
In your case
Hello.
As far as I know, postgres will update the index with each DML statement, so
the scenario you present should not be a problem by itself. However, having a
table updated that frequently can be a problem if the table grows too much and
is not well indexed.
If the table is small, you can c
Looks like one has the appropiate cast operator, while the other hasn't. Have
you tried doing the same, on both server, on an empty database created from
template0?
Regards,
Alvaro Aguayo
Jefe de Operaciones
Open Comb Systems E.I.R.L.
Oficina: (+51-1) 3377813 | RPM: #034252 / (+51) 995540103
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 wr
hat sound like a good plan. I will trying tomorrow, because need maintenance
window.
To do back up I can use something like
bdr_dump -Fp -h localhost -U postgres mydb -f /tmp/mydb.data > --data-only
--exclude-table='bdr_*
volga629
From: "Alvaro Aguayo Garcia-Rada"
To:
M: #034252 / (+51) 995540103 | RPC: (+51)
954183248
Website: www.ocs.pe
- Original Message -----
From: "Slava Bendersky"
To: "Alvaro Aguayo Garcia-Rada"
Cc: "pgsql-general" , "John R Pierce"
Sent: Thursday, 31 March, 2016 12:28:09 AM
Subject: Re: [GENER
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, where you can have a secondary server which
serves as a read-only replica, and can be rpomoted to master
M: #034252 / (+51) 995540103 | RPC: (+51)
954183248
Website: www.ocs.pe
- Original Message -
From: "Sridhar N Bamandlapally"
To: "Alvaro Aguayo Garcia-Rada"
Cc: "John R Pierce" , "PostgreSql-general"
Sent: Tuesday, 29 March, 2016 10:09:10
S
Some time ago I had to setup a replicated file system between multiple linux
servers. I tried everything I could based on postgres, including large objects,
but everything was significantly slower than a regular filesystem.
My conclussion: postgres is not suitable for storing large files efficie
Hi. I think pgpool-II can do that job for you. It's a middleware, so you can
use it without even changing your app code(but your postgres configuration). It
suppoerts many clustering functions, including replication, failover, and a lot
more; it also supports partitioning. so that may be suitabl
Hi. I currently have two servers in different geographical locations; both of
them are replicating with Postgres-BDR, that's OK. However, I need two more
servers to get a read only replication of only some tables from the master ones.
At first I tried with Slony, but it just didn't work(don't kn
23 matches
Mail list logo
