pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedError while setting up streaming replication, postgres 9.0-beta 4
3+ messages / 2 participants
[nested] [flat]
* Error while setting up streaming replication, postgres 9.0-beta 4
@ 2010-08-23 19:07 fazool mein <fazoolmein@gmail.com>
2010-08-23 19:17 ` Re: Error while setting up streaming replication, postgres 9.0-beta 4 Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: fazool mein @ 2010-08-23 19:07 UTC (permalink / raw)
To: pgsql-admin
Hello everyone,
OS = Linux Suse, sles 11, 64-bit
Postgres version = 9.0 beta-4
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, and the secondary has correct connection
information to the primary in 'resolve.conf'.
Any pointers?
Thanks.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Error while setting up streaming replication, postgres 9.0-beta 4
2010-08-23 19:07 Error while setting up streaming replication, postgres 9.0-beta 4 fazool mein <fazoolmein@gmail.com>
@ 2010-08-23 19:17 ` Tom Lane <tgl@sss.pgh.pa.us>
2010-08-23 19:57 ` Re: Error while setting up streaming replication, postgres 9.0-beta 4 fazool mein <fazoolmein@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2010-08-23 19:17 UTC (permalink / raw)
To: fazool mein <fazoolmein@gmail.com>; +Cc: pgsql-admin
fazool mein <fazoolmein@gmail.com> writes:
> 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,
You need to do that *before* taking your base backup. The WARNING above
indicates that the backup was taken with an inadequate wal_level
setting.
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Error while setting up streaming replication, postgres 9.0-beta 4
2010-08-23 19:07 Error while setting up streaming replication, postgres 9.0-beta 4 fazool mein <fazoolmein@gmail.com>
2010-08-23 19:17 ` Re: Error while setting up streaming replication, postgres 9.0-beta 4 Tom Lane <tgl@sss.pgh.pa.us>
@ 2010-08-23 19:57 ` fazool mein <fazoolmein@gmail.com>
0 siblings, 0 replies; 3+ messages in thread
From: fazool mein @ 2010-08-23 19:57 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
Great! I made the base backup again as you said, and its working now.
Thanks.
On Mon, Aug 23, 2010 at 12:17 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> fazool mein <fazoolmein@gmail.com> writes:
> > 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,
>
> You need to do that *before* taking your base backup. The WARNING above
> indicates that the backup was taken with an inadequate wal_level
> setting.
>
> regards, tom lane
>
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2010-08-23 19:57 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-08-23 19:07 Error while setting up streaming replication, postgres 9.0-beta 4 fazool mein <fazoolmein@gmail.com>
2010-08-23 19:17 ` Tom Lane <tgl@sss.pgh.pa.us>
2010-08-23 19:57 ` fazool mein <fazoolmein@gmail.com>
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