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 1ta53N-00Fy6r-JN for pgsql-hackers@arkaria.postgresql.org; Tue, 21 Jan 2025 03:35:50 +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 1ta53M-00AXqL-Kk for pgsql-hackers@arkaria.postgresql.org; Tue, 21 Jan 2025 03:35:48 +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 1ta53M-00AXqD-BU for pgsql-hackers@lists.postgresql.org; Tue, 21 Jan 2025 03:35:48 +0000 Received: from mail-yb1-xb33.google.com ([2607:f8b0:4864:20::b33]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ta53J-000eCx-1g for pgsql-hackers@lists.postgresql.org; Tue, 21 Jan 2025 03:35:48 +0000 Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-e3c9ec344efso7442070276.2 for ; Mon, 20 Jan 2025 19:35:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737430544; x=1738035344; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2kHPlZMcvyR+Xj+PymjQLL5QRJqKQBK0Y2bKi3SMt20=; b=BiWSZPaNyWskVik+mol3bhDnDh5uFiAaqCzOGQGCwn+bcdFVxrBtu6vpMczRaCb7pT aXqLTG96l1xnnlT89orG2M+u10tX85dzylNEoDTFJ5iAzpSvyZffvuKDjdHBVPYZbUAI sb+JmFQ65C01GcTsLlmh8zcxzob8rlHjTe/peWV34QcNZUl35BrDVPa2+nPEX7bR5GlH 2XPJwxfkROLw1FOSem8Sypl3p+RuD3tzPtCGA//kony6KjW3MCkj/Niwhflzd9FVlTau FNpoP9vomYxY4ou4fksAQz18NZ7Q/PlqqQmKtqwpy9EKU/foZ3oXDNIUqwWwU4oTg16G vBUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737430544; x=1738035344; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2kHPlZMcvyR+Xj+PymjQLL5QRJqKQBK0Y2bKi3SMt20=; b=OnwI4ei703Y4L6xdq0ngDYSF5fqkJFPIXlDO9hmwDtLesmP/J6OS/7hmX4biQyj7Pj aKWfqx9fe+Nh8SZ0iwmo7E4EBNPsPsBkRTgAQD1TAYYwxBVc8QphwCBgwDcHtd7J4On0 S7+U53lIcs2eFzNj1rXwbdeq80nwOO1oI+FDr0hnDK4WftRHLogbJbV7eTC6YuEKkPBN tbJiBMOmIHOYVR1xbEaUtoEDsio9vTXIFeoY1ZZJbJLlUpnaLn2MHldTVRAhifgnKt/z zMgi0BVOAsq1WkSy77D53k+01dR0AJWW904XeyzwdrAvwYqxTSjy/Ld/vuyRYAlF3w13 SPwQ== X-Forwarded-Encrypted: i=1; AJvYcCVbRT2ezJJlUAZ0jSTQjyDY01BD/k84nkbZDFSogwNKlo5EwyoBm/Meg0tDCekgHOhT53BhPW1Tw2qkpWAn@lists.postgresql.org X-Gm-Message-State: AOJu0Yyd6oVmMdaFAHD01Q8TbWyDvwWxx9nBGEGjVxAfnpImKT+0Zsi/ iACB+TZOYhwCxED6HQk7QVOJ4uH2IedwDSpoYFVyOwAxO+MJvMirTXGD7bH/8sxuZTppdjjSzhW gJRAem316Vxgqf97yd4mou06P6Pw= X-Gm-Gg: ASbGncslz3Tt9ApCz1IH074YLgzlfi64/M5MoCvBtcHh5GBEaS5c8s4yM/hCgMqZeIl f2Ij5GoRRfx2bbXLZilNRhqT75W1nt4xay6Q78v4YkbY6bF1WjnIFofhjZ6wV X-Google-Smtp-Source: AGHT+IF5Oc3vaA6UXkLyPAkgE1JTTxoGgzBw3j6B1a0rHsvCI5VRqEIEfFnPzgusYzADWrIQ9Ytcfi3jcFxMc3BQ4PI= X-Received: by 2002:a05:690c:3749:b0:6ef:61b9:dfca with SMTP id 00721157ae682-6f6eb6a1805mr118733437b3.20.1737430544171; Mon, 20 Jan 2025 19:35:44 -0800 (PST) MIME-Version: 1.0 References: <5ecc35f5-1111-47fc-8a02-36d89490a50d@iki.fi> <24b3deb6-a732-4256-847a-560f4bf39d59@iki.fi> <4535f3aa-3220-4760-b1f5-2bc91f248e03@iki.fi> <2bc58592-9d74-4af0-bdd1-1a88e8683f7c@iki.fi> In-Reply-To: From: wenhui qiu Date: Tue, 21 Jan 2025 11:35:33 +0800 X-Gm-Features: AbW1kvYPyWn2rIUE3P8V2FV7poXl_0ijxMh_gmWhpLst8sRRaFR59duN3pndIXg Message-ID: Subject: Re: POC: make mxidoff 64 bits To: Maxim Orlov Cc: Heikki Linnakangas , Alexander Korotkov , Postgres hackers Content-Type: multipart/alternative; boundary="000000000000684b96062c2f1265" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000684b96062c2f1265 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable HI Maxim > Looks like there is a bit of a pause in the discussion. Here is a small update. Consider v12. > No major changes, rebase to the actual master and a squash of multiple commits to make a > patch set easy to reviewer. > AFAICs, we are reached a consensus on a core patch for switching to 64 bits offsets. The > only concern is about more comprehensive test coverage for pg_upgrade, is it? Agree ,When upgrading meets extremes (oldestOffsetKnown=3D=3Dfalse.) Just follow the solution mentioned by Heikki Linnakangas. Thanks On Thu, Jan 16, 2025 at 9:32=E2=80=AFPM Maxim Orlov wro= te: > Looks like there is a bit of a pause in the discussion. Here is a small > update. Consider v12. > No major changes, rebase to the actual master and a squash of multiple > commits to make a > patch set easy to reviewer. > > AFAICs, we are reached a consensus on a core patch for switching to 64 > bits offsets. The > only concern is about more comprehensive test coverage for pg_upgrade, is > it? > > -- > Best regards, > Maxim Orlov. > --000000000000684b96062c2f1265 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
HI Maxim=C2=A0
> Looks like there is a bit of = a pause in the discussion. Here is a small update. Consider v12.
= > No major changes, rebase to the actual master and a squash of multiple= commits to make a
> patch set easy to reviewer.

> A= FAICs, we are reached a consensus on a core patch for switching to 64 bits = offsets. The
> only concern is about more comprehensive test c= overage for pg_upgrade, is it?
Agree ,When upgrading meets = extremes (oldestOffsetKnown=3D=3Dfalse.)= =C2=A0Just follow the solution mentioned by Heikki Linnakangas.

Thanks

On Thu, Jan 16, 2025= at 9:32=E2=80=AFPM Maxim Orlov <or= lovmg@gmail.com> wrote:
<= div>Looks like there is a bit of a pause in the discussion. Here is a small= update. Consider v12.
No major changes, rebase to the actual mas= ter and a squash of multiple commits to make a
patch set easy to = reviewer.

AFAICs, we are reached a consensus on a core patch for swi= tching to 64 bits offsets. The
only concern is about more compreh= ensive test coverage for pg_upgrade, is it?

--
<= div dir=3D"ltr">
Best regards,
Maxim Orlov.
--000000000000684b96062c2f1265--