Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Downloads
Home
>
mailing lists
pg_basebackup fails on inactive slave - Mailing list pgsql-general
From
Stanislav Antic
Subject
pg_basebackup fails on inactive slave
Date
February 24, 2015
13:55:58
Msg-id
CAHNe0nTEEGaDuo0E2dCp=jLvKPdyECzPNmSvLV-oBdzJ2uo60w@mail.gmail.com
Whole thread
Raw
List
pgsql-general
Tree view
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
pgsql-general
by date:
Previous
From:
Mitu Verma
Date:
24 February 2015, 10:15:27
Subject:
Leap second impact on postgreSQL on June 30 2015
Next
From:
Guillaume Drolet
Date:
24 February 2015, 15:07:35
Subject:
Re: Sequences not moved to new tablespace
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
I confirm that I have read and accepted PostgresPro’s
Privacy Policy
.
I agree to get Postgres Pro discount offers and other marketing communications.
✖
×
×
Everywhere
Documentation
Mailing list
List:
all lists
pgsql-general
pgsql-hackers
buildfarm-members
pgadmin-hackers
pgadmin-support
pgsql-admin
pgsql-advocacy
pgsql-announce
pgsql-benchmarks
pgsql-bugs
pgsql-chat
pgsql-cluster-hackers
pgsql-committers
pgsql-cygwin
pgsql-docs
pgsql-hackers-pitr
pgsql-hackers-win32
pgsql-interfaces
pgsql-jdbc
pgsql-jobs
pgsql-novice
pgsql-odbc
pgsql-patches
pgsql-performance
pgsql-php
pgsql-pkg-debian
pgsql-pkg-yum
pgsql-ports
pgsql-rrreviewers
pgsql-ru-general
pgsql-sql
pgsql-students
pgsql-testers
pgsql-translators
pgsql-www
psycopg
Period
anytime
within last day
within last week
within last month
within last 6 months
within last year
Sort by
date
reverse date
rank
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
By continuing to browse this website, you agree to the use of cookies. Go to
Privacy Policy
.
I accept cookies