Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dIFBV-0002Ea-2v for pgsql-admin@arkaria.postgresql.org; Tue, 06 Jun 2017 14:10:13 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dIFBU-0000C4-1m for pgsql-admin@arkaria.postgresql.org; Tue, 06 Jun 2017 14:10:12 +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 1dIF9g-0005RC-Fo for pgsql-admin@postgresql.org; Tue, 06 Jun 2017 14:08:20 +0000 Received: from mail-lf0-x22e.google.com ([2a00:1450:4010:c07::22e]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1dIF9e-0002e9-3i for pgsql-admin@postgresql.org; Tue, 06 Jun 2017 14:08:20 +0000 Received: by mail-lf0-x22e.google.com with SMTP id p189so20472854lfe.2 for ; Tue, 06 Jun 2017 07:08:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=HlYCQt6WoyjPEZ/5XRnxpp2eOgj0hr8uELq35UoGeyw=; b=OT3YHMzHXHOzfjmg1VewbRkyymENrAZgMrF8PmN72nEKi9uRYJcOZNbz6ts6DXuJKN irTyZ2iEDRTzwfkXPq/7sBS3DqxWdX7nPAN+O+ipmvVg0aNkrpnPWkoAGxl3XvGDL0S2 DJjSCNe0FfNMhBLZNLmhfh9vIJMtwT2V3jArJUmzE5MaWBjnNtXKQR9ilQ6ebNHWj8EZ OlieVazoW6nqThYtQ90bTzL59Jlw8dnFu4RdlndHgisBcCS7d74AZMXqlu1KgJxiJLZ7 PRc45Mlb04KghrbIjpdejjs2kR4h+9bXN+rfa5c9qAeFl79xX8DHjkS8v4vZ4lkb0DJ1 xTQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=HlYCQt6WoyjPEZ/5XRnxpp2eOgj0hr8uELq35UoGeyw=; b=US5f1zGlR5byDAwqpLGc/zFECuTr5GeNDIobGSYf6FVVAGoiu64Tj8bWXSNwza072X voLcrw3c5oCi0vQpOhk3nGMqXlMyLuJni2yTXJt+CNAwT5hptiqpwoioYUrH4aNnusf5 zXPcOrhAFqU1HewCbfseiOeLS/nnQkgP2uUSjGd6uMdtc5niZimdJ8Upf9nJ2MhaGjur 6a4crlZ1AYt3YhVVN6IuiMRHSTkze3Z6zB5UPX654xSSb/Ob0VuDe0Y4ijtFKgfffCYK YsAgMFPoielfM2WzkEPcXq6NKiy+VbIbhE/xzhAlRGZHRq6P8LzX8lqjhEqMWHrHJj6w UEzw== X-Gm-Message-State: AODbwcB6GpvPkvNaQjSEGcf2ZfTsZa2pSJk0U+IsKIsCQwO0QjrahIAE gR3178pDwdxEcllzrLk= X-Received: by 10.46.1.219 with SMTP id f88mr2753359lji.119.1496758096483; Tue, 06 Jun 2017 07:08:16 -0700 (PDT) Received: from seb.koffice.internal (koffice.avito.ru. [195.151.206.25]) by smtp.gmail.com with ESMTPSA id x199sm1027232lfa.13.2017.06.06.07.08.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jun 2017 07:08:15 -0700 (PDT) From: Sergey Burladyan To: Thorsten =?utf-8?Q?Sch=C3=B6ning?= Cc: pgsql-admin@postgresql.org Subject: Re: Does Postgres ever write to tables without file system timestamps getting updated? References: <143511646.20170606100454@am-soft.de> <1599962113.20170606153203@am-soft.de> <08328348.20170606155614@am-soft.de> Date: Tue, 06 Jun 2017 17:08:14 +0300 In-Reply-To: <08328348.20170606155614@am-soft.de> ("Thorsten \=\?utf-8\?Q\?Sch\?\= \=\?utf-8\?Q\?\=C3\=B6ning\=22's\?\= message of "Tue, 6 Jun 2017 15:56:14 +0200") Message-ID: <871sqx5hv5.fsf@seb.koffice.internal> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -2.7 (--) 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 Thorsten Sch=C3=B6ning writes: > From the following very old data files, mostly unchanged for > days/weeks, e.g. 2613.13 got transferred because of different > checksums, while 2613.10 didn't: How many bytes was changed in this file? --=20 Sergey Burladyan --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin