Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cVin9-0001YP-CD for pgsql-performance@arkaria.postgresql.org; Mon, 23 Jan 2017 17:52:31 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cVin8-0000jL-VG for pgsql-performance@arkaria.postgresql.org; Mon, 23 Jan 2017 17:52:31 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cVilS-0007Iz-TC for pgsql-performance@postgresql.org; Mon, 23 Jan 2017 17:50:47 +0000 Received: from tamriel.snowman.net ([72.66.115.51]) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cVilQ-0003R9-DK for pgsql-performance@postgresql.org; Mon, 23 Jan 2017 17:50:45 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id 0FAFB5F796; Mon, 23 Jan 2017 12:49:44 -0500 (EST) Date: Mon, 23 Jan 2017 12:49:43 -0500 From: Stephen Frost To: Simon Riggs Cc: Jeff Janes , julyanto SUTANDANG , Dinesh Chandra 12108 , "pgsql-performance@postgresql.org" Subject: Re: Backup taking long time !!! Message-ID: <20170123174943.GL18360@tamriel.snowman.net> References: <0fb0c8c3f69340a3a7d70b1c39fa2b2c@cyient.com> <20170122145740.GE18360@tamriel.snowman.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Jr+vfydpun11/55L" 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: 12:48:12 up 198 days, 19:12, 5 users, load average: 0.16, 0.18, 0.15 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 --Jr+vfydpun11/55L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Simon Riggs (simon@2ndquadrant.com) wrote: > On 23 January 2017 at 17:12, Jeff Janes wrote: > >> 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. > > > > Correct. Unfortunately it is a very common myth that it does cause > > PostgreSQL to stop writing to the base dir. >=20 > Never heard that one before. Wow. Who's been saying that? Well, this conversation started because of such a comment, so at least one person on this thread (though I believe that's been clarified sufficiently now). > It's taken me years to hunt down all invalid backup memes and terminate t= hem. A never-ending and thankless task, so, my thanks to you for your efforts. :) > Never fails to surprise me how many people don't read the docs. +1MM. Thanks again! Stephen --Jr+vfydpun11/55L Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJYhkI3AAoJEO1sijiDR2RVxWsP/0vO420/54w1sZZN9qtEz4s5 96TtyEUV5H4zTmTcfYRhBCJ1hsEU7Ae+n75qE3SsXIbJT3vTdATUD6lrRBJS1dmU Q5OzZeI+BXhL8VocT24pEoFIxvSw8AUvsrJfKrdDd+Wehq971GTmjBAByBxzFT0K KUwcIAx9yqQUz0zGhnCwB9cEQjwSzkXaTMPe1/LeylBQCIF0P14yZmCNvW9EvAwt tUl7k96iH+dnPCH293cBWnY1boX+3ygygILefo4uOBNH9E8yT4n73EwsVjk75lTw coy0s+arFarq3jQg12tW4tkM/zbuUgRHV19J7OAwH96+98adIsbzmARFzmcLOqn/ 1JzTc8zhAc20UkTyQ6Qntt9G+1uFizziQkBI8utb4aUhJQBaQ4Vf3SCbk5k20rPp 0PKfg5Y85LMPJP/5V22Ve7u5Pb2QYiYNX9lMCMu93UHBIusSloV0YVetFpwCQti5 RLSgD7YaoX3Ic0smdwX6JncKdet+nNUZz0pyaw8l0lI1N2Fudb8697PyHeE2d6Nk NeZKfAC7EcDi0YoVebILrE2oYkmfkqmlU55LPno5+l8DTiEDWBqGL9U5NGvcPg1x xN1Fs6yPCoPMitXexf4mNr5mMrxp4e685QP8htCc+eDFLJwjjuvyD1Jm8KwZ/ITN KXnOk5hZFqk+VBbjggfF =l9Ll -----END PGP SIGNATURE----- --Jr+vfydpun11/55L--