I'm curious why you are focused on the archive on the primary?
Postgres docs do not say that during initial recovery you need a backup
history file. But It is required during initial recovery. That's why I am
focused on it.
You lost 0002001C.00512178.backup. That means your
On Wed, Mar 04, 2009 at 03:14:51PM -0500, Ray Stell wrote:
On Wed, Mar 04, 2009 at 03:06:12PM -0500, Ray Stell wrote:
Testing pg_standby in 8.3.6. I've gotten this standby into some sort of
bind. It seems like it may be waiting for some WAL. How can I tell
what it is waiting on? I
On Wed, Mar 04, 2009 at 05:05:19PM -0500, Yauheni Labko wrote:
No. %f is the WAL filename which is needed by the server to start recovery.
my recovery command is:
restore_command='/usr/local/pgsql/bin/pg_standby /data/pgsql/wals/alerts_oamp
%f %p %r
my recovery command is:
restore_command='/usr/local/pgsql/bin/pg_standby
/data/pgsql/wals/alerts_oamp %f %p %r
/home/postgresql/log/alerts_oamp/recovery.log'
You gave the recovery command, not the archive command. And give a piece of
log file where primary server performs archiving WAL
On Thu, Mar 05, 2009 at 10:04:44AM -0500, Yauheni Labko wrote:
You gave the recovery command, not the archive command.
I'm curious why you are focused on the archive on the primary?
Is there some logic in the archive process that could cause the recovery to
be looking for
Testing pg_standby in 8.3.6. I've gotten this standby into some sort of
bind. It seems like it may be waiting for some WAL. How can I tell
what it is waiting on? I don't really know how this works, so I may
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes
On Wed, 2009-03-04 at 15:06 -0500, Ray Stell wrote:
Testing pg_standby in 8.3.6. I've gotten this standby into some sort of
bind. It seems like it may be waiting for some WAL. How can I tell
what it is waiting on? I don't really know how this works, so I may
Looks like you were cut off
On Wed, Mar 04, 2009 at 03:06:12PM -0500, Ray Stell wrote:
Testing pg_standby in 8.3.6. I've gotten this standby into some sort of
bind. It seems like it may be waiting for some WAL. How can I tell
what it is waiting on? I don't really know how this works, so I may
say something silly.
On Wed, 2009-03-04 at 15:14 -0500, Ray Stell wrote:
On Wed, Mar 04, 2009 at 03:06:12PM -0500, Ray Stell wrote:
Testing pg_standby in 8.3.6. I've gotten this standby into some sort of
bind. It seems like it may be waiting for some WAL. How can I tell
what it is waiting on? I don't
On Wed, Mar 04, 2009 at 08:31:16PM +, Simon Riggs wrote:
You've set archive_timeout?
no, but new WAL files seem to be getting created and replicated to the standby,
just the pg_standby
command seems snagged on something. I probably have done something dumb,
ready, fire, aim. I'm
For some reason it is looking for 0002001C.00512178.backup
file which is not the WAL file.
Are you sure that you made initial recovery properly?
Yauheni Labko (Eugene Lobko)
Junior System Administrator
Chapdelaine Co.
(212)208-9150
On Wednesday 04 March 2009 03:14:51 pm Ray
On Wed, Mar 04, 2009 at 03:41:06PM -0500, Yauheni Labko wrote:
For some reason it is looking for 0002001C.00512178.backup
file which is not the WAL file.
Are you sure that you made initial recovery properly?
I could have fouled this in any number of ways. Like I said
I'm
No. %f is the WAL filename which is needed by the server to start recovery.
0002001C.00512178.backup will give you start and end of WAL
segment, the WAL filename containing this segment and your label to identify
where it might be. That's why I asked you about your backup.
Btw i think you may remove %r from the restore command.
Yauheni Labko (Eugene Lobko)
Junior System Administrator
Chapdelaine Co.
(212)208-9150
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
14 matches
Mail list logo
