From: | Stanislav Antic <stanislav(dot)antic(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | pg_basebackup fails on inactive slave |
Date: | 2015-02-24 10:55:52 |
Message-ID: | CAHNe0nTEEGaDuo0E2dCp=jLvKPdyECzPNmSvLV-oBdzJ2uo60w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have PostgreSQL 9.2.6 (pgdg-92-centos.repo) on CentOS 6.4 amd64.
I have a problem when I do pg_basebackup on slave with following options
pg_basebackup -w -U replication -h 127.0.0.1 -p 5432\
-D /mnt/basebackups_last/ -F p -l "backup_24.02.2015" -x
I got message:
pg_basebackup: could not get transaction log end position from server:
FATAL: could not find any WAL files
-x - will by default take WALs on end of basebackup.
Is it normal because database master/slave aren't all that active at a time
of taking this
basebackup that basebackup on slave fail with this message?
Should I remove "-x" option, it's not strictly needed because I have a
service that is fetching
wals that can be combined with basebackups?
Thanks
--
Stanislav Antic
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Drolet | 2015-02-24 12:07:10 | Re: Sequences not moved to new tablespace |
Previous Message | Mitu Verma | 2015-02-24 07:15:17 | Leap second impact on postgreSQL on June 30 2015 |