Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UhS05-0000s5-0V for pgsql-admin@arkaria.postgresql.org; Tue, 28 May 2013 22:04:13 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UhS04-00014u-Dd for pgsql-admin@arkaria.postgresql.org; Tue, 28 May 2013 22:04:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UhS02-00014o-Tj for pgsql-admin@postgresql.org; Tue, 28 May 2013 22:04:11 +0000 Received: from qmta05.emeryville.ca.mail.comcast.net ([2001:558:fe2d:43:76:96:30:48]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1UhRzo-0005a0-B8 for pgsql-admin@postgresql.org; Tue, 28 May 2013 22:04:09 +0000 Received: from omta08.emeryville.ca.mail.comcast.net ([76.96.30.12]) by qmta05.emeryville.ca.mail.comcast.net with comcast id hZFb1l0070FhH24A5a3sHV; Tue, 28 May 2013 22:03:52 +0000 Received: from homie ([38.98.177.132]) by omta08.emeryville.ca.mail.comcast.net with comcast id ha3h1l00c2rmZlA8Ua3k56; Tue, 28 May 2013 22:03:50 +0000 Received: by homie (Postfix, from userid 1000) id 2056D18287C; Tue, 28 May 2013 18:03:41 -0400 (EDT) To: Virupaksha Kanjilal Cc: pgsql-admin@postgresql.org Subject: Re: WAL files required to make base backup consistent References: From: Jerry Sievers Date: Tue, 28 May 2013 17:03:41 -0500 In-Reply-To: (Virupaksha Kanjilal's message of "Wed\, 22 May 2013 14\:30\:26 -0700") Message-ID: <87ppwa3goy.fsf@comcast.net> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1369778632; bh=qx0XiO+ODoIe9IJqG+z0XwTi0WagCrtiHDSE1PVHMd4=; h=Received:Received:Received:To:Subject:From:Date:Message-ID: MIME-Version:Content-Type; b=grJ9dYwKVEWwN/hlOexn2eCt/X84hUtTiTNjAVmfWqSWaix76BQoK6tPYJU+flYTK XBq6Vb/8ZtPg3F/nYEwPqU89RH+GTYQYsOwNWo7j0F3iJqvbIYzyQffCo4Rb+/3C3z L2dwZSOR0DzFIXLMc3616ZwqRS0IQUF6Rx815p7GISCwAtjjCq0XTv8HpA+rrt9HBZ Es0EMsdPKB9tf5N/4rLg+90ECxAyR7DlbymL76DfzCGLefqDpgtHTZRTXpNYODEb8z kfDvlqGBmZtgZgUF6UTrVgw0EdOgmAquSgxo45xt1AqBYZUsjOd0nSNBZkt1d2uVa3 jYKAdiWzbPNuw== X-Pg-Spam-Score: -1.8 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Virupaksha Kanjilal writes: > Hi > > I perform a pg_basebackup with tar option and do not bring in the WAL segments created during the backup. Now I want > to make the backup a consistent copy and for that I need the WAL segments. How can I know which all WAL segments to > apply to bring the backup to a consistent state? Look in your WAL repository for files named *.backup. The prefix part will match the name of a regular WALf file from when the backup was started and the .backup file itself will contain some human readable text indicating the last WAL segment that you'll need for a consistent recovery. HTH > Thanks > Viru > -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin