> > 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 >
OK, so, could you guide me where to start on this feature ? regards, Marcos
