Subject: Re: Strange times in WAL files in archive directory (9.3)
To: pgsql-admin@postgresql.org
References: <58871A66.306@matrix.gatewaynet.com>
 <58873609.4030004@matrix.gatewaynet.com> <13126.1485264550@sss.pgh.pa.us>
From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
Message-ID: <588759C8.3090209@matrix.gatewaynet.com>
Date: Tue, 24 Jan 2017 15:42:32 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <13126.1485264550@sss.pgh.pa.us>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Hi Tom,

On 24/01/2017 15:29, Tom Lane wrote:
> The larger issue here is that you're confusing the function of an archive area with that of the active WAL directory. The server will prune what is in the active WAL directory and does not want your 
> help. In an archive directory, I'd expect the files to have monotonic timestamps corresponding to the times you copied them over to the archive, so you could rely on the timestamp sequence there. 
> regards, tom lane 
I would be silly to mess around with pg_xlog. I was talking about the archive directory. *There* is where I noticed the inconsistencies. In my second post in this thread I used pg_xlog to show the 
difference in timestamp of the same md5-wise files between the two systems (pg_xlog vs archive dir).

-- 
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin