On 24-May-20 15:48, Stephen Frost wrote:
That really shouldn't be possible. I'm very curious as to exactly what
happened that resulted in your primary/replica being 'out of sync', as
you say.
Hi Stephen,
Actually this was more a hypothetical question to find a solution in
case some day one
Hello
On 2020-05-25 15:50, Laurenz Albe wrote:
On Fri, 2020-05-22 at 08:02 -0500, Ted Toth wrote:
Will RLS be applied to data being retrieved via a FDW?
ALTER FOREIGN TABLE rp_2019 ENABLE ROW LEVEL SECURITY;
ERROR: "rp_2019" is not a table
Doesn't look good.
Yours,
Laurenz Albe
Actually
On 5/24/20 10:30 PM, Nico De Ranter wrote:
Unfortunately not. I discovered the issue rather late. The last working
backup is about 2 months old.
Well first it is entirely possible this is not the only corruption in
the database.
Second you are probably going to have to reach out to the Bacul
On Fri, 2020-05-22 at 08:02 -0500, Ted Toth wrote:
> Will RLS be applied to data being retrieved via a FDW?
ALTER FOREIGN TABLE rp_2019 ENABLE ROW LEVEL SECURITY;
ERROR: "rp_2019" is not a table
Doesn't look good.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
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
Hi!
How to set logical replication for all user databases in cluster so that
when new database is added or new tables are added to database they will
start replicate automatically ?
I think that it would be good if you spend some time reading the
documentation on this stuff, particularly the pa
