Re: Finalizing logical replication limitations as well as potential features

2018-01-08 Thread Alvaro Hernandez
On 05/01/18 05:35, Joshua D. Drake wrote: On 01/04/2018 01:26 PM, Alvaro Herrera wrote: Joshua D. Drake wrote: We just queue/audit the changes as they happen and sync up the changes after the initial sync completes. This already happens.  There is an initial sync, and there's logical decodi

Re: Finalizing logical replication limitations as well as potential features

2018-01-04 Thread Joshua D. Drake
On 01/04/2018 01:26 PM, Alvaro Herrera wrote: Joshua D. Drake wrote: We just queue/audit the changes as they happen and sync up the changes after the initial sync completes. This already happens. There is an initial sync, and there's logical decoding that queues any changes that exist "after"

Re: Finalizing logical replication limitations as well as potential features

2018-01-04 Thread Alvaro Herrera
Joshua D. Drake wrote: > We just queue/audit the changes as they happen and sync up the changes > after the initial sync completes. This already happens. There is an initial sync, and there's logical decoding that queues any changes that exist "after" the sync's snapshot. What you seem to want

Re: Finalizing logical replication limitations as well as potential features

2018-01-04 Thread Joshua D. Drake
On 12/21/2017 06:15 PM, Craig Ringer wrote: On 22 December 2017 at 05:24, Joshua D. Drake > wrote: -Hackers, Lastly, I noted that a full sync of a replication set is performed by a COPY, this is fine for small sets but if we have a large data set

Re: Finalizing logical replication limitations as well as potential features

2017-12-21 Thread Craig Ringer
On 22 December 2017 at 05:24, Joshua D. Drake wrote: > -Hackers, > > > As I continue to test Logical Replication and its native capabilities I > have found the following: > > > It appears it is not possible to do this: > > publisher->public.foo replicates to subscriber->private.foo > > This one s