Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dIFV3-0003Y2-OJ for pgsql-admin@arkaria.postgresql.org; Tue, 06 Jun 2017 14:30:25 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dIFV3-0004zi-Ao for pgsql-admin@arkaria.postgresql.org; Tue, 06 Jun 2017 14:30:25 +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 1dIFTG-0001Sc-J1 for pgsql-admin@postgresql.org; Tue, 06 Jun 2017 14:28:34 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dIFTE-0007nP-3n for pgsql-admin@postgresql.org; Tue, 06 Jun 2017 14:28:33 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 95E3721266; Tue, 6 Jun 2017 14:28:29 +0000 (UTC) Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo02-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fa7Z_ceoNbta; Tue, 6 Jun 2017 14:28:29 +0000 (UTC) Received: from [192.168.2.16] (unknown [8.39.228.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id D419121264; Tue, 6 Jun 2017 14:28:27 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Does Postgres ever write to tables without file system timestamps getting updated? From: scott ribe In-Reply-To: <1599962113.20170606153203@am-soft.de> Date: Tue, 6 Jun 2017 08:28:25 -0600 Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <143511646.20170606100454@am-soft.de> <1599962113.20170606153203@am-soft.de> To: =?utf-8?Q?Thorsten_Sch=C3=B6ning?= X-Mailer: Apple Mail (2.3273) X-Pg-Spam-Score: -1.9 (-) 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 On Jun 6, 2017, at 7:32 AM, Thorsten Sch=C3=B6ning = wrote: >=20 > Obviously I wasn't clear enough: Postgres is not running and my > problem is with files and their timestamps in the past. So regarding > the timestamps the files didn't change for weeks and the files have > the same size and timestamp in the source and my backup. But if I > calculate hash sums of those files the results may differ, so rsync > using checksums will back them up, although the files claim that they > haven't changed for days/weeks. You were clear, it's too early in the morning here. You seem to be assuming that the files were changed close to the time you f= ound the problem; as far as I can tell that's not actually true, they could= have been changed back at the time of the file timestamps, and could have = been out-of-sync for a while, right? My suggestion to use pg_start_backup is irrelevant to the exact problem you= 're describing. The documentation for it does describe a good way to get a = file-based backup, without stopping the server, and you might want to check= into that. You could also look at pg_base_backup. -- Scott Ribe scott_ribe@elevated-dev.com (303) 722-0567 --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin