Re: Error while setting up streaming replication, postgres 9.0-beta 4
От | fazool mein |
---|---|
Тема | Re: Error while setting up streaming replication, postgres 9.0-beta 4 |
Дата | |
Msg-id | AANLkTikL3uNDzUGFJ+xwDoO2RUh9RX7XwiMCLuwtsB4O@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Error while setting up streaming replication, postgres 9.0-beta 4 (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-admin |
Great! I made the base backup again as you said, and its working now.
Thanks.
Thanks.
On Mon, Aug 23, 2010 at 12:17 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
fazool mein <fazoolmein@gmail.com> writes:You need to do that *before* taking your base backup. The WARNING above
> I'm trying to test streaming replication. I set up a primary and secondary.
> The primary starts normal, but when I start the standby, it doesn't start
> up. The log looks like this:
> LOG: database system was interrupted while in recovery at log time
> 2010-08-23 13:30:43 EDT
> HINT: If this has occurred more than once some data might be corrupted and
> you might need to choose an earlier recovery target.
> LOG: entering standby mode
> WARNING: WAL was generated with wal_level=minimal, data may be missing
> HINT: This happens if you temporarily set wal_level=minimal without taking
> a new base backup.
> FATAL: hot standby is not possible because wal_level was not set to
> "hot_standby" on the master server
> HINT: Either set wal_level to "hot_standby" on the master, or turn off
> hot_standby here.
> LOG: startup process (PID 5875) exited with exit code 1
> LOG: aborting startup due to startup process failure
> Note that I have checked multiple times that 'wal_level' is set to
> 'hot_standby' on the primary,
indicates that the backup was taken with an inadequate wal_level
setting.
regards, tom lane
В списке pgsql-admin по дате отправления: