On Wed, Sep 22, 2021 at 10:27 PM Euler Taveira <eu...@eulerto.com> wrote: > > On Wed, Sep 22, 2021, at 1:18 AM, Amit Kapila wrote: > > On Tue, Sep 21, 2021 at 4:21 PM Marcos Pegoraro <mar...@f10.com.br> wrote: > > No, I´m talking about that configuration you can have on standby servers > recovery_min_apply_delay = '8h' > > > oh okay, I think this can be useful in some cases where we want to avoid data > loss similar to its use for physical standby. For example, if the user has by > mistake truncated the table (or deleted some required data) on the publisher, > we can always it from the subscriber if we have such a feature. > > Having said that, I am not sure if we can call it a restriction. It is more > of a TODO kind of thing. It doesn't sound advisable to me to keep growing the > current Restrictions page [1]. > > It is a new feature. pglogical supports it and it is useful for delayed > secondary server and if, for some business reason, you have to delay when data > is available. >
What kind of reasons do you see where users prefer to delay except to avoid data loss in the case where users unintentionally removed some data from the primary? -- With Regards, Amit Kapila.
