Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eew7X-00082O-Ij for pgsql-docs@arkaria.postgresql.org; Fri, 26 Jan 2018 05:00:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eew7V-0001lw-1B for pgsql-docs@arkaria.postgresql.org; Fri, 26 Jan 2018 05:00:09 +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 1eew7U-0001kq-KV for pgsql-docs@lists.postgresql.org; Fri, 26 Jan 2018 05:00:08 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eew7L-0003ZU-Hr for pgsql-docs@lists.postgresql.org; Fri, 26 Jan 2018 05:00:07 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 28DB520C24; Thu, 25 Jan 2018 23:59:57 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Thu, 25 Jan 2018 23:59:57 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=oN0DFj U9+P4cSDOGFmO1yvU+UBvDv3jBTsu7VKLzj6Q=; b=eKRbKrRkuDJadgTVaoJ2bm RQRU3CXAPFhu8SfD4hTJYmufyUyAQ7ZeAJYhxlGICeVNx61alyw4GYsxlk5vthwD VUizfEJsr48Z1uqqH7aNsMSaM5a9W5/o9324bYmdWMFZiCQxKw2jPIlUqL6peWBK OvIShcxKa9caIm/2VO4YwO0QvhLKK99N1kNudVieOu/eWMql32Ntj4j0Jzjn55AQ rS56bIrUjneUEKsgh/ikOctYgamWq/rbUlzYMHL2GX+2OUnIX7n4abqWh6DMdz59 mPN8FW0cnJKCqfKX7rHPAF3/DnQ2eHnX2y+TGstFlEzV8wdjUKE3Zj5vaCii0Azg == X-ME-Sender: Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id D3E51241E0; Thu, 25 Jan 2018 23:59:56 -0500 (EST) Subject: Re: Can take filesystem bkp of pg data folder when server is running To: vidyasagarps@gmail.com, pgsql-docs@lists.postgresql.org References: <20180123060015.7407.32905@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Thu, 25 Jan 2018 23:59:56 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180123060015.7407.32905@wrigleys.postgresql.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 1/23/18 01:00, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/backup-file.html > Description: > > I am running postgresql 10 on mac and was experimenting on backup and > restore features of PG 10 > I certainly can take FS backup of the cluster with TAR when server is > running and with ACTIVE client connections [dummy begin; statement] > > This seems against the documented explanation for FS backup method and its > limitation. > > Is there something I am missing here? It might work sometimes, especially if you are trying it on a dummy setup, but it's not going to work in general. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services