From: Steve Singer <steve@ssinger.info>
To: Petr Jelinek <petr@2ndquadrant.com>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Craig Ringer <craig@2ndquadrant.com>
Subject: Re: pglogical - logical replication contrib module
Date: Sat, 16 Jan 2016 14:55:50 -0500
Message-ID: <569AA046.40109@ssinger.info> (raw)
In-Reply-To: <56992762.1090409@2ndquadrant.com>
References: <5685BB86.5010901@2ndquadrant.com>
<569151D5.3060003@ssinger.info>
<5692B798.2050002@ssinger.info>
<56992762.1090409@2ndquadrant.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 01/15/2016 12:07 PM, Petr Jelinek wrote:
> That's bug, fixed.
>
Can you posted an updated patch with whatever fixes you have so far made?
> There are several statuses the table goes through, during the COPY
> it's in synchronizing status, so next logical step seemed to be
> synchronized. Maybe it should be renamed to 'replicating' instead as
> that's what it actually means (table has finished synchronization and
> is now replicating normally).
>
I agree 'replicating' is clearer
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: steve@ssinger.info, petr@2ndquadrant.com, craig@2ndquadrant.com
Subject: Re: pglogical - logical replication contrib module
In-Reply-To: <569AA046.40109@ssinger.info>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox