From: | Stephen Kuntz <Skuntz(at)pelmorex(dot)com> |
---|---|
To: | MirrorX <mirrorx(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: WAL replay asking for very old WAL |
Date: | 2016-03-07 16:38:40 |
Message-ID: | DM2PR0401MB108884AC78CFF0E77273F8F1ACB10@DM2PR0401MB1088.namprd04.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Sorry for the confusion, I am by no means a postgresql guru.
In my other slave servers I don't have the message:
2016-03-07 16:23:36 UTC ERROR: cannot execute UNLISTEN during recovery
2016-03-07 16:23:36 UTC STATEMENT: unlisten *
In the logs once they are caught up to the master. It also doesn't seem to switch to standby mode properly and stream from the master. When I restart, it replays the WAL files since the last restart from the archive. This data should have been streamed from the master, no?
standby_mode = 'on'
primary_conninfo = 'user=<replicationuser> password=<mypassword> host=masterserver port=5432 sslmode=prefer sslcompression=1 krbsrvname=postgres'
restore_command = 'copy "\\\\archivefileserver\\BACKUP\\DatabaseBackups\\wal_archive\\%f" "%p"'
Stephen Kuntz | Systems Administrator
Pelmorex Media Inc.
T: 905.829.1159 x1376
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of MirrorX
Sent: Monday, March 7, 2016 11:13 AM
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] WAL replay asking for very old WAL
sorry i don't follow.
the server will stay in recovery mode as long as a recovery.conf file exists and the host is set up to receive xlogs via streaming from the master. this seems to be the case according to the logs, if i am not wrong.
what it is you want to happen? the server to stop applying records and come online in r/w mode?
in this case you could promote the server. or if you want just to apply some wal files and then come online then i think you have misconfigured your recovery.conf. i would suggest you paste here what your recovery.conf contains and what the objective is
Best,
--
View this message in context: http://postgresql.nabble.com/WAL-replay-asking-for-very-old-WAL-tp5891050p5891074.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
From | Date | Subject | |
---|---|---|---|
Next Message | MirrorX | 2016-03-07 17:01:11 | Re: WAL replay asking for very old WAL |
Previous Message | MirrorX | 2016-03-07 16:12:36 | Re: WAL replay asking for very old WAL |