On 7 September 2017 at 21:16, milist ujang wrote:
> Hi Craig,
>
> On Wed, Sep 6, 2017 at 4:07 PM, Craig Ringer
> wrote:
>
>>
>> You could drop and re-create the replication slot, I guess. But your
>> nodes would be hopelessly out of sync and need
Hi Craig,
On Wed, Sep 6, 2017 at 4:07 PM, Craig Ringer wrote:
>
> You could drop and re-create the replication slot, I guess. But your nodes
> would be hopelessly out of sync and need manual resync (with data
> replication disabled) of one node vs another.
>
Thanks for
On 6 September 2017 at 08:47, milist ujang wrote:
> Hi Craig
>
> On Wed, Sep 6, 2017 at 7:21 AM, Craig Ringer
> wrote:
>>
>>
>> BDR can, see bdr.skip_changes_upto .
>>
>> Unluckily my bdr is 0.9.3
>
>
>> But PostgreSQL's logical decoding requires a
Hi Craig
On Wed, Sep 6, 2017 at 7:21 AM, Craig Ringer wrote:
>
>
> BDR can, see bdr.skip_changes_upto .
>
> Unluckily my bdr is 0.9.3
> But PostgreSQL's logical decoding requires a contiguous WAL stream to
> maintain a valid catalog_xmin and restart_lsn, so it'll still
On 6 September 2017 at 01:52, milist ujang wrote:
> Hi all,
>
> due to space issue and high volume transaction, some wal segments removed
> from pg_xlog on bdr environment.
>
What, you deleted them?
> I had played streams and goldengate (oracle product) , that at
Hi all,
due to space issue and high volume transaction, some wal segments removed
from pg_xlog on bdr environment.
warning log at node1 saying "requested WAL segment . has already been
removed" following Connection reset by peer.
log at node2 :
Sending replication command: START_REPLICATION