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
xlog min recovery request ... is past current point ... - Mailing list pgsql-general
From
Alberto Bussolin
Subject
xlog min recovery request ... is past current point ...
Date
August 2, 2013
21:21:20
Msg-id
642289871.5039.1375453991062.JavaMail.root@mailserver.edistar.com
Whole thread
Raw
Responses
Re: xlog min recovery request ... is past current point ...
(Michael Paquier <michael.paquier@gmail.com>)
List
pgsql-general
Tree view
Hi,
i was testing a point in time recovery on a postgres 9.1.9.
When processing the xlog i found out these log messages (on postgres.log):
postgres@postgres[[local]] FATAL: the database system is starting up
@[] LOG: restored log file "000000020000026B000000D5" from archive
@[] LOG: redo starts at 26B/D50049F0
@[] WARNING: xlog min recovery request 26B/EB529C40 is past current point 26B/D5758198
@[] CONTEXT: writing block 0 of relation base/2831418/257279491_vm xlog redo insert: rel 1663/1425752962/2572579716; tid 3235/118
The restore procedure completed correctly and all the data was restored.
May i ignore this warning or is it something i didn't realise?
Alberto Bussolin
pgsql-general
by date:
Previous
From:
Alvaro Herrera
Date:
02 August 2013, 21:13:33
Subject:
Re: TOC errors
Next
From:
Jerry Sievers
Date:
02 August 2013, 21:35:24
Subject:
Re: TOC errors
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
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