Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eJJMv-00068o-IE for pgsql-admin@arkaria.postgresql.org; Mon, 27 Nov 2017 13:22:41 +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 1eJJMv-0002Av-3g for pgsql-admin@arkaria.postgresql.org; Mon, 27 Nov 2017 13:22:41 +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 1eJJMu-0002Al-T8 for pgsql-admin@lists.postgresql.org; Mon, 27 Nov 2017 13:22:40 +0000 Received: from mailout.easymail.ca ([64.68.200.34]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eJJMn-0003fY-0w for pgsql-admin@postgresql.org; Mon, 27 Nov 2017 13:22:40 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 50D2ACEAD5; Mon, 27 Nov 2017 13:22:30 +0000 (UTC) Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (emo01-pco.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QTfhYJNRLtg; Mon, 27 Nov 2017 13:22:30 +0000 (UTC) Received: from [192.168.2.16] (unknown [8.39.228.117]) (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 28603CEAA7; Mon, 27 Nov 2017 13:22:27 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Clear FS caches after postgresql stops From: scott ribe In-Reply-To: Date: Mon, 27 Nov 2017 06:22:25 -0700 Cc: "pgsql-admin@postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <3DF72595-3A7B-457E-A922-95860398F365@elevated-dev.com> References: To: =?utf-8?Q?Jakub_Jedelsk=C3=BD?= X-Mailer: Apple Mail (2.3273) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Nov 27, 2017, at 4:16 AM, Jakub Jedelsk=C3=BD = wrote: >=20 > Is it possible, that Postgresql leave some data in memory after its = stop? Not unless you turned fsynch off in the conf, and you really should NOT = be doing that for production. Remember that rsync normally compares timestamp & size, and that = timestamps are often only 1-second precision. Thus it's possible for = changes to be skipped unless you use the -c flag. -- Scott Ribe https://www.linkedin.com/in/scottribe/ (303) 722-0567