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 1uWmUr-001L3h-Ss for pgsql-bugs@arkaria.postgresql.org; Wed, 02 Jul 2025 01:42:49 +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 1uWmUp-009EZG-MB for pgsql-bugs@arkaria.postgresql.org; Wed, 02 Jul 2025 01:42:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uWmUp-009EZ0-Dq for pgsql-bugs@lists.postgresql.org; Wed, 02 Jul 2025 01:42:48 +0000 Received: from m16.mail.163.com ([220.197.31.4]) by makus.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1uWmUl-005377-1C for pgsql-bugs@lists.postgresql.org; Wed, 02 Jul 2025 01:42:46 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; bh=eclxvQSeJ4ouWIQMIz2qzP4Y+2oIFx1PT+V8BAj1bOE=; b=PcJ38XwUTpVxjwGhW19aOGRLDHWCHISpAO+ssum0fSk7rVJBbFA6UrFdZ2a1sj zLP30K8ROkdkZwy1G+daAG7u9UTsa0CWFnum7Rwqs+jvOhrmEbuxcCdXhQUb2ilQ Ut+BwvpSyqV0WG429/E6ojwaJTQ007tdj9bLJOKh+hHRY= Received: from lovely-coding (unknown []) by gzga-smtp-mtada-g0-2 (Coremail) with SMTP id _____wAXec6IjmRohpm9Bw--.20021S3; Wed, 02 Jul 2025 09:42:33 +0800 (CST) From: Andy Fan To: Fujii Masao Cc: Alvaro Herrera , zoulx1982@163.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16931: source code problem about commit_ts In-Reply-To: (Fujii Masao's message of "Mon, 12 Apr 2021 00:09:45 +0900") References: <20210409224241.GA32072@alvherre.pgsql> Date: Wed, 02 Jul 2025 01:42:32 +0000 Message-ID: <87ecuzmkqf.fsf@163.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-CM-TRANSID: _____wAXec6IjmRohpm9Bw--.20021S3 X-Coremail-Antispam: 1Uf129KBjvJXoW7Ar4kArWDGryfXr1ruF45KFg_yoW8Gw18pw 47Aa47KF4DXF1Uur1vqr1UXFyUuFWqqF1UWwnF9FyxZF1ruFyfKFsagF4a9FWjvF18Ga4q qF1Yk3ZYgF1kua7anT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x07U2fOcUUUUU= X-Originating-IP: [113.250.190.7] X-CM-SenderInfo: x2klx3xlid0iqsrtqiywtou0bp/xtbBhQR+U2hkhtK6xAAAsK List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=-=-= Content-Type: text/plain Fujii Masao writes: Hi, > On 2021/04/10 7:42, Alvaro Herrera wrote: >> On 2021-Mar-24, Fujii Masao wrote: >> >>> diff --git a/src/backend/access/rmgrdesc/committsdesc.c b/src/backend/access/rmgrdesc/committsdesc.c >>> index 7ebd3d35ef..26bad44b96 100644 >>> --- a/src/backend/access/rmgrdesc/committsdesc.c >>> +++ b/src/backend/access/rmgrdesc/committsdesc.c >>> @@ -38,31 +38,6 @@ commit_ts_desc(StringInfo buf, XLogReaderState *record) >>> appendStringInfo(buf, "pageno %d, oldestXid %u", >>> trunc->pageno, trunc->oldestXid); >>> } >>> - else if (info == COMMIT_TS_SETTS) >> You have not pushed this one, right? I think we should do it now. > > Thanks for the ping! Pushed! Did this commit(08aa89b326261b669648df97d4f2a6edba22d26a) forget to remove struct xl_commit_ts_set? After it, there is no reference to xl_commit_ts_set. So Is it better clean them as well? typedef struct xl_commit_ts_set { TimestampTz timestamp; RepOriginId nodeid; TransactionId mainxid; /* subxact Xids follow */ } xl_commit_ts_set; #define SizeOfCommitTsSet (offsetof(xl_commit_ts_set, mainxid) + \ (When going through commit_ts.h, these code makes me think there is a dedicated xlog for commit_ts, but the fact isn't, the commit_ts is recorded in xl_xact_commit, removing dead code could be useful for such case). -- Best Regards Andy Fan --=-=-= Content-Type: text/x-diff Content-Disposition: attachment; filename=v1-0001-Remove-xl_commit_ts_set.patch