Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cVJbT-0006ww-Nh for pgsql-performance@arkaria.postgresql.org; Sun, 22 Jan 2017 14:58:47 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cVJbT-0007TT-2H for pgsql-performance@arkaria.postgresql.org; Sun, 22 Jan 2017 14:58:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cVJbS-0007TN-Lr for pgsql-performance@postgresql.org; Sun, 22 Jan 2017 14:58:46 +0000 Received: from tamriel.snowman.net ([72.66.115.51]) by magus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cVJbP-0000eF-Ba for pgsql-performance@postgresql.org; Sun, 22 Jan 2017 14:58:46 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 67DF05F796; Sun, 22 Jan 2017 09:57:40 -0500 (EST) Date: Sun, 22 Jan 2017 09:57:40 -0500 From: Stephen Frost To: julyanto SUTANDANG Cc: Dinesh Chandra 12108 , "pgsql-performance@postgresql.org" Subject: Re: Backup taking long time !!! Message-ID: <20170122145740.GE18360@tamriel.snowman.net> References: <0fb0c8c3f69340a3a7d70b1c39fa2b2c@cyient.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3C1+oG8NxxW+Hf7i" Content-Disposition: inline In-Reply-To: X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/3.13.0-91-generic (x86_64) X-Uptime: 09:55:14 up 197 days, 16:19, 4 users, load average: 0.01, 0.06, 0.10 User-Agent: Mutt/1.5.21 (2010-09-15) X-Pg-Spam-Score: -5.1 (-----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org --3C1+oG8NxxW+Hf7i Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * julyanto SUTANDANG (julyanto@equnix.co.id) wrote: > CORRECTION: >=20 > "you might you pg_start_backup to tell the server not to write into the > DATADIR" >=20 > become >=20 > "you might *use* pg_start_backup to tell the server not to write into the > *BASEDIR*, actually server still writes but only to XLOGDIR " Just to make sure anyone reading the mailing list archives isn't confused, running pg_start_backup does *not* make PG stop writing to BASEDIR (or DATADIR, or anything, really). PG *will* continue to write data into BASEDIR after pg_start_backup has been called. The only thing that pg_start_backup does is identify an entry in the WAL stream, from which point all WAL must be replayed when restoring the backup. All WAL generated from that point (pg_start_backup point) until the pg_stop_backup point *must* be replayed when restoring the backup or the database will not be consistent. Thanks! Stephen --3C1+oG8NxxW+Hf7i Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJYhMhkAAoJEO1sijiDR2RVj3kP/A0KrtICl/D9KuG5EMClgyZH YKH00KN3a9/7BOkyp4JbasC8nJoBw64MmrwF5ANVSNzmG/53VuLHDtNjdE/VaWwd 2ODxzCIIagidMe2iVJewJiYlhJV/Z2NvhVW44flUGHWP77wkGpOKxuvMwFl/ADhh 2tfmToRcFyixy8njPBfdAVTiKGX503Rs3rzbqY58w8DcyaGPpkn8QuOEzuNKtvZQ WSBOKieoMblQVzq6YSLf7BGNJOv7rBqy5DeeYPa0Bctl/PVw8yvI9I118LCudmQB FCFROuz2GDo672wxnY0zQUAjRfQaOxntXNl2a6njuLf4gNKCVcIbOJYZgCWguoQq QAxm4vdqyIBCWabSTTBYUyaSCqwohWaCy7Y/5Hc9d+1lEkV8SulFzRnb8EE+aO/v 98s/LSCSRXNv5uIRGcPMa3kpLQjGkTVMukeE+w9o1uMvG0CYUJ43QHtRCLeTmz0p b4/ryTzmas/rSFZCs2uniriAM9NtQhbR1k6UAsUXMT+MpD+LYH4thZfz4vzN62Q9 5oCy9Ww6x2tul+13MddUDXW8EtiwVQwEinJ9xWkfwa5VtNGwux+/1VPIjan1CVV7 /sCRB8bU4XhmqFwLVw9jhX0lBiZHN9cHF2TZvD0cn7V/AxgyX1zWhfMxcDwQIkX5 Mj998Mh3xF4AhzYq87S2 =g9x5 -----END PGP SIGNATURE----- --3C1+oG8NxxW+Hf7i--