On 2020-05-25 10:19, Anders Bøgh Bruun wrote:
Thank you for that clarification. It helps me understand how things work
a lot better.
I know this might be a bit off topic, but my challenge here is that we
are using Patroni (by using Zalando's postgres-operator for Kubernetes),
and any replicatio
Thank you for that clarification. It helps me understand how things work a
lot better.
I know this might be a bit off topic, but my challenge here is that we are
using Patroni (by using Zalando's postgres-operator for Kubernetes), and
any replication slot not created by Patroni, seems to be removed
On 2020-05-20 17:16, Anders Bøgh Bruun wrote:
[67] LOG: logical replication apply worker for subscription
"widgets_sub" has started
[67] DEBUG: connecting to publisher using connection string
"dbname=testdb host=master port=5432 user=repuser password=abc123"
[67] ERROR: could not receive data
Fair question, I should have been more elaborate.
When I have the creation of a replication slot, before I insert any data
into the table in my example (the SQL-file named "broken" in my gist),
after I then create the subscription on the receiving side, it does the
initial sync of data and then th
On 2020-05-19 09:22, Anders Bøgh Bruun wrote:
I have run into a (to me) weird issue with logical replication. We are
running Zalandos postgres-operator in our Kubernetes clusters and have
recently had a use-case where we wanted to start doing logical
replication of select tables to a data wareh
Hi,
I have run into a (to me) weird issue with logical replication. We are
running Zalandos postgres-operator in our Kubernetes clusters and have
recently had a use-case where we wanted to start doing logical replication
of select tables to a data warehouse, also running postgres. It worked as
exp
