RE: pg_wal fills up on big update query

2019-08-09 Thread Daniel Fink (PDF)
understanding of how postgres works under the hood. Best Regards, Daniel -Original Message- From: Luca Ferrari [mailto:fluca1...@gmail.com] Sent: Friday, August 9, 2019 3:58 PM To: Daniel Fink (PDF) Cc: pgsql-general Subject: Re: pg_wal fills up on big update query On Wed, Aug 7, 2019 at 3:34

RE: pg_wal fills up on big update query

2019-08-09 Thread Daniel Fink (PDF)
...@gmail.com] *Sent:* Wednesday, August 7, 2019 4:22 PM *To:* Daniel Fink (PDF) *Cc:* pgsql-general@lists.postgresql.org *Subject:* Re: pg_wal fills up on big update query On Aug 7, 2019, at 7:34 AM, Daniel Fink (PDF) wrote: Hi all, I have a migration where I · Add a new nullable column

pg_wal fills up on big update query

2019-08-07 Thread Daniel Fink (PDF)
Hi all, I have a migration where I · Add a new nullable column to a table · update almost every row in this big table (8 million rows) from another table where I set this new column I have also a replication setup running. The database has a size of around 20GB. While the

RE: bdr replication breaks down

2019-02-25 Thread Daniel Fink (PDF)
ailto:aagu...@opensysperu.com] Sent: Monday, February 11, 2019 2:21 PM To: Daniel Fink (PDF) Cc: pgsql-general Subject: Re: bdr replication breaks down What's the command you are running to trigger such behaviour? Regards, Alvaro Aguayo Jefe de Operaciones Open Comb Systems E.I.R.L. (+51-1) 337-7813 Anexo 4002

RE: BDR 1.0: background worker wants to start that should not be there

2019-02-25 Thread Daniel Fink (PDF)
, it removed the failing workers. Thanks for your help. Best Regards, Daniel -Original Message- From: Alvaro Aguayo Garcia-Rada [mailto:aagu...@opensysperu.com] Sent: Tuesday, February 12, 2019 4:15 PM To: Daniel Fink, PDF Cc: pgsql-general Subject: Re: BDR 1.0: background worker wants to start

BDR 1.0: background worker wants to start that should not be there

2019-02-12 Thread Daniel Fink (PDF)
Hi all, After I used bdr.bdr_part_by_node_names(*p_nodes text[]*) and removed the nodes from bdr.bdr_nodes table I still get log errors about the nonexistent pg_replication_slot: < 2019-02-12 06:26:21.166 PST >LOG: starting background worker process "bdr

RE: bdr replication breaks down

2019-02-11 Thread Daniel Fink (PDF)
snapshot 1214 snapshot 2608 snapshot 2608 relcache 23783862 snapshot 2608 rmgr: Standby len (rec/tot): 44/76, tx: 0, lsn: 7D/2E314530, prev 7D/2E3143B0, bkp: , desc: nontransactional message with 35 bytes *From:* Daniel Fink (PDF) [mailto:daniel.f...@pdf.com] *Sent:* Monday

bdr replication breaks down

2019-02-11 Thread Daniel Fink (PDF)
Hi all, I have a bdr replication setup that worked fine until recently. But it seems like one command cannot be replicated, and it breaks down the whole process on all hosts where it is sent to. I appended part of the log file, it gets repeated over and over. Can I somehow omit this command

Enabling bdr in multiple databases on the same postgresql instance/cluster

2018-10-23 Thread Daniel Fink (PDF)
Hi all, I already have a running cluster of BDR nodes. Now we want to add an additional database on the same hosts. Can I just create a new database and then create/join nodes as in this description: http://bdr-project.org/docs/1.0.3/quickstart-enabling.html Best Regards, *DANIEL