Hi.
You have deleted the node from BDR setup, but you still have to delete it from
the postgres logical replication:
SELECT * FROM pg_replication_slots;
SELECT pg_drop_replication_slot('YOURSLOT');
As a remark, based on my BDR experience, when your cluster has been damaged,
your best option is
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
www.ocs.pe
- Original Message -
From: "Daniel Fink (PDF)"
To: "pgsql-general"
Sent: Monday, 11 February, 2019 05:18:30
Subjec
Hi. Not sure if the fastest, but the first that comes up to my mind is using
pg_dump and psql. First you create your new database, then you run
this(replacing as needed):
pg_dump OLDDB | psql NEWDB
Saludos,
Alvaro Aguayo
Jefe de Operaciones
Open Comb Systems E.I.R.L.
Oficina: (+51-1) 3377813
Hi.
As far as I know, it's not currently possible. Maybe recompiling, but that
could not be the best for production environment. I suppose this is this way
becuase postgres is designed to expect a certain folder structure for it's data
folder, and configuration files are considered part of it.
Not sure if such case would corrup the backup, but I won't make a backup just
by copying the data directory.
Use pg_basebackup instead, it's safer
Regards,
Alvaro Aguayo
Operations Manager
Open Comb Systems E.I.R.L.
Office: (+51-1) 3377813 | Mobile: (+51) 995540103 | (+51) 954183248
Web: www.o
Should work with no problem, but I would not recommend it. You may not be able
to setup a service(SysV or systemd) to automatically start postgres, and
updating version could be troublesome.
Regards,
Alvaro Aguayo
Operations Manager
Open Comb Systems E.I.R.L.
Office: (+51-1) 3377813 | Mobile:
Let's see There are two major issues when writing business logic in
database:
1. Portability. Being tied to a single database engine is not always a good
idea. When you write business logic in database, you have to write and maintain
your store procedures for every database engine you want
Hi.
Based on my experience, you will probably have no problem when migrating
applications from PG 9.x to 9.6. Same for 8.x to 9.6.
I recently migrated an application installed on around 100 servers from 8.4 to
9.6, and the only problem I had was regarding database encoding, more
specifically
What do you have on your postgresql logs, on the server?
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
Raghavendra Rao J S V wrote
Not sure if this may help you. A few months ago, I made an automated OpenSUSE
installer which also had to install PostgreSQL 9.6 server using the RHEL PGDG
releases. There's no YUM there, so I did it instead with RPM files directly.
The RPM files I included on my autoinstall ISO are the followin
10 matches
Mail list logo