pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tharmarajah, Sam <sambavan.tharmarajah@usask.ca>
To: John Scalia <jayknowsunix@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Req. for some help with resolving the error "pg_basebackup: could not get WAL end position from server: FATAL:  requested WAL segment"
Date: Mon, 5 Dec 2016 20:27:10 +0000
Message-ID: <0bdba7c255474ff6973bbf5ba1ef9661@Mail02.usask.ca> (raw)
In-Reply-To: <11CEA700-3307-4425-8ADF-6E819447889E@gmail.com>
References: <873181a7a9164ffe8b74c6e425a1a724@Mail02.usask.ca>
	<11CEA700-3307-4425-8ADF-6E819447889E@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

Hi John,

Thank you for the feed back. Presently it is taking around 1hr to finish the backups. We have the wal_keep_segments set to 50. Is there way to adjust the segment size to be more than 16MB? At times I notice in the pg_xlog, there are 10-15 segments on an invocation point.


Thanx,
Sam

From: John Scalia [mailto:jayknowsunix@gmail.com]
Sent: Monday, December 05, 2016 1:52 PM
To: Tharmarajah, Sam <sambavan.tharmarajah@usask.ca>
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Req. for some help with resolving the error "pg_basebackup: could not get WAL end position from server: FATAL: requested WAL segment"

More than likely your keep_wal_segments setting is too low. How long is the pg_basebackup taking? Remember that segments are generated about every 5 minutes, so if the backup takes an hour, you need at least 12 segments stored. At 2 hours, you need 24 etc., I'd set the value to about 12.2 segments/hour of backup.
--
Jay


Sent from my iPad

On Dec 5, 2016, at 1:57 PM, Tharmarajah, Sam <sambavan.tharmarajah@usask.ca<mailto:sambavan.tharmarajah@usask.ca>> wrote:
Hi

I am a newbie to postgres. We are on postgres 9.1 running on RedHat 6.  When we do the postgres backups we are noticing the following errors

pg_basebackup: could not get WAL end position from server: FATAL:  requested WAL segment  000000010000020B00000040 has already been removed

But when I look into pg_xlog, I notice

000000010000020B00000040.00000118.backup


May I know how to resolve this error? Are the backups done with these errors, recoverable?


Thanks in advance for your support.

Thanx,
Sam






view thread (5+ messages)  latest in thread

Message-ID: <0bdba7c255474ff6973bbf5ba1ef9661@Mail02.usask.ca>
Permalink:  ../0bdba7c255474ff6973bbf5ba1ef9661@Mail02.usask.ca/
Also on:    postgresql.org/message-id/0bdba7c255474ff6973bbf5ba1ef9661@Mail02.usask.ca

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: sambavan.tharmarajah@usask.ca, jayknowsunix@gmail.com
  Subject: Re: Req. for some help with resolving the error "pg_basebackup: could not get WAL end position from server: FATAL:  requested WAL segment"
  In-Reply-To: <0bdba7c255474ff6973bbf5ba1ef9661@Mail02.usask.ca>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox