Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r2hah-000RUq-JU for pgsql-hackers@arkaria.postgresql.org; Tue, 14 Nov 2023 00:47:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r2haf-003WEn-Sq for pgsql-hackers@arkaria.postgresql.org; Tue, 14 Nov 2023 00:47:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r2haf-003WEc-JB for pgsql-hackers@lists.postgresql.org; Tue, 14 Nov 2023 00:47:41 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r2hac-006J15-WB for pgsql-hackers@lists.postgresql.org; Tue, 14 Nov 2023 00:47:40 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=+cvQK+jN09oMURiEUMhIDvvIMZ2+kNH0UdKcWeIAYKc=; b=4tQ0W /bnImYmaURupbdMV+qcwvlOro8/pP/mPZOF6qfQXeTA8EjAPf/8iFqUNp1F/HL3HhK9UieJEzp8bp QNjYq9TwIfwkJWy/hAyM0IMU7k+3cAXFGCRgvnRwyXNwyKghHaiomyjMfSx91pTbXsL/9+vs7HXdP fohsT1Ueku3GLVz5YxS9gAuoihdHvkAFFioqcCpkgik+/J5RQl/0s0LuLUQWb6aT+8u1nD5TEHCnT UD4MOQFXaFbyzzsI79kfZ3g8MtEV5K9YDq4bzIr298EpOv87hg4XOZ3Oztg1NQzLoTLVf1IEaULm8 O7ukg3qzgsrbYL3N35qva5Zy25OSg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1r2haa-0000SB-0y; Mon, 13 Nov 2023 19:47:36 -0500 Date: Mon, 13 Nov 2023 19:47:36 -0500 From: Bruce Momjian To: Kyotaro HORIGUCHI Cc: pgsql-hackers@lists.postgresql.org Subject: Re: Lifetime of commit timestamps Message-ID: References: <20180622.172132.230342845.horiguchi.kyotaro@lab.ntt.co.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180622.172132.230342845.horiguchi.kyotaro@lab.ntt.co.jp> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jun 22, 2018 at 05:21:32PM +0900, Kyotaro HORIGUCHI wrote: > Hello. > > I don't find any description in the documentation about the > guaranteed lifetime of commit timestamps. I think they are > preserved until corresponding xid goes beyond the freeze horizen, > even though they are actually preserved longer for several > reasons. > > If it is not, I think such description is required in > pg_xact_commit_timestamp(). > diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml > index 5dce8ef178..633e488cec 100644 > --- a/doc/src/sgml/func.sgml > +++ b/doc/src/sgml/func.sgml > @@ -18029,7 +18029,8 @@ SELECT collation for ('foo' COLLATE "de_DE"); > These functions mainly provide information about when the transactions > were committed. They only provide useful data when > configuration option is enabled > - and only for transactions that were committed after it was enabled. > + and only for transactions that were committed after it was enabled. Commit > + timestamps for frozen tuples are removed at vacuum time. > Is this documentation change still relevant? -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.