Re: [COMMITTERS] pgsql: Introduce replication progress tracking infrastructure.

2015-05-01 Thread Andres Freund
On 2015-04-30 13:56:08 +0900, Michael Paquier wrote: > On Thu, Apr 30, 2015 at 2:37 AM, Andres Freund wrote: > > Introduce replication progress tracking infrastructure. > > [...] > > Some comments about the docs: > 1) "the the": > + > +Create a replication origin with the the passe

Re: [COMMITTERS] pgsql: Introduce replication progress tracking infrastructure.

2015-04-29 Thread Michael Paquier
On Thu, Apr 30, 2015 at 2:37 AM, Andres Freund wrote: > Introduce replication progress tracking infrastructure. > [...] Some comments about the docs: 1) "the the": + +Create a replication origin with the the passed in external +name, and create an internal id for it. +

Re: [COMMITTERS] pgsql: Introduce replication progress tracking infrastructure.

2015-04-29 Thread Andres Freund
On 2015-04-29 15:49:10 -0400, Andrew Dunstan wrote: > > On 04/29/2015 01:37 PM, Andres Freund wrote: > >Introduce replication progress tracking infrastructure. > > > > > > > This appears to have broken some builds (see for example >

Re: [COMMITTERS] pgsql: Introduce replication progress tracking infrastructure.

2015-04-29 Thread Andrew Dunstan
On 04/29/2015 01:37 PM, Andres Freund wrote: Introduce replication progress tracking infrastructure. This appears to have broken some builds (see for example ) by using UINT16_MAX instead of PG_UINT1

[COMMITTERS] pgsql: Introduce replication progress tracking infrastructure.

2015-04-29 Thread Andres Freund
Introduce replication progress tracking infrastructure. When implementing a replication solution ontop of logical decoding, two related problems exist: * How to safely keep track of replication progress * How to change replication behavior, based on the origin of a row; e.g. to avoid loops in bi