Re: Streaming replication with sync slave, but disconnects due to missing WAL segments

From: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Jeff Janes *EXTERN*" <jeff(dot)janes(at)gmail(dot)com>, "Mads(dot)Tandrup(at)schneider-electric(dot)com" <Mads(dot)Tandrup(at)schneider-electric(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Streaming replication with sync slave, but disconnects due to missing WAL segments
Date: 2013-06-05 08:30:42
Message-ID: A737B7A37273E048B164557ADEF4A58B17B9AA24@ntex2010a.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jeff Janes wrote:
> On Tue, Jun 4, 2013 at 6:25 AM, <Mads(dot)Tandrup(at)schneider-electric(dot)com> wrote:
>> I have a question about sync streaming replication.
>>
>> I have 2 postgresql 9.1 servers set up with streaming replication. On the
>> master node the slave is configured as a synchronous standby. I've verified
>> that pg_stat_replication shows sync_state = sync for the slave node.
>>
>> It all seems to work fine. But I have noticed that sometimes when I restore
>> backups created by pg_dump. The slave node will disconnect with the message
>> in the postgresql log:
>
> You cannot use pg_dump to set up a database for receiving streaming replication.
>
> For that it must be a physical copy, not a logical copy which is what pg_dump generates.

I think you misunderstood - he restores a dump on
the *primary* and that makes replication fall over
because it cannot catch up.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Panneerselvam Posangu 2013-06-05 09:30:58 Synonyms in PostgreSQL 9.2.4
Previous Message Panneerselvam Posangu 2013-06-05 08:29:39 Synonyms in PostgreSQL 9.2.4