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 1slTeZ-0081dL-90 for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Sep 2024 13:33:03 +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 1slTeY-00BrF4-4y for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Sep 2024 13:33:02 +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 1slTeX-00BrEv-Ra for pgsql-hackers@lists.postgresql.org; Tue, 03 Sep 2024 13:33:02 +0000 Received: from mail-wr1-x430.google.com ([2a00:1450:4864:20::430]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1slTeV-000Spb-TR for pgsql-hackers@lists.postgresql.org; Tue, 03 Sep 2024 13:33:01 +0000 Received: by mail-wr1-x430.google.com with SMTP id ffacd0b85a97d-374ba74e9b6so2871788f8f.0 for ; Tue, 03 Sep 2024 06:33:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725370378; x=1725975178; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=3f/mekubkf8Z60/7I3gH5StAVIR1OfnawNT41OvWqoA=; b=hORQ+dFYbNX6vwvwXR56FcdIC99+U7RQ3HV9w0czjoOhvL9XYq3OurGacvloQz/e2C 2qY7fawPS55UrR1CEkYDyd64DdqWXXsr3O7TfVYgCqEd2dg2A3bTwLvStWxrLJkUPH+r sR0Xjwwk+iStG2x64CabZLk1I8k4fpl3i/6i3KQuDNsScVVE3NAnNBbdWXkzQr6xWLoW 4NLOdj+mBuAV8AOF4hKm01Sd2wNY6TSnPxXYiYOpkWINFC14Ihtt4TSx5n6xVvfMrfx7 ExcvYUZdSkh3HlL/2arKHXi6pV8pDuevofExyssOdYEwM39MP86eicjqybLYR1yC3pPi b4sA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725370378; x=1725975178; h=content-transfer-encoding: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=3f/mekubkf8Z60/7I3gH5StAVIR1OfnawNT41OvWqoA=; b=xNhKR6vaT/IjgRlwnc240YAUQWFP036orLzcMA7Hy74Cz/0HoELXJWH9YAZ4OfCQnI yhbXkaskT8GT4xXIuVMSUOaFa36jWVKQW0ugjAFvmRCwRc3bKxU/oB7/DqaJ5qZSYhTN EMZx+esoAPBVWhkjYyNWXShhxPVJkUvhA2FJi7K1NidlTSJru7SnPPbmeLt2F2bluIZN J+JIEjRW8w0VDb3EtgaUC2upYC31NisBIiVYnZlwhAbOjAwwBJivbgZRWkxyJaaoV5sJ Us5+Is8vspRGvf+r4takNNPoFgrUp9J03dlUAY0CQnm/KxmG8jixChfp8FUR6pLklLCD lYjA== X-Forwarded-Encrypted: i=1; AJvYcCVn/FuzwuZGCyDc3GP+4sYHpX2UQgkQ8OR7kJwSmbdrv605u7mFc3igIj3l4OLpmSYIysg677DNMIqAuCua@lists.postgresql.org X-Gm-Message-State: AOJu0YyUi3D3mK7Dea8FGoSZ1vcPWZw2NUjeGlex4L394DAMw+nxHiyP 4iiFM4D3m1Kr+vWrn8cwwJQXK7KxPvLgFzK0GuncGQ7QN/zW5lFs3mnpr4YrIBlQNG8UuOO2h02 A+FWxg12g+NmNUwy47BFdx7W9iU0= X-Google-Smtp-Source: AGHT+IEUPV8e73ILq1N5V8Yzf/YqHIUf75eyr3WSTrTpiZ5Xr2+1ckPFjo00qUsnk+0mQpdpDqDZ2FssH4zI6SaaGJ0= X-Received: by 2002:adf:f550:0:b0:374:bd01:707c with SMTP id ffacd0b85a97d-374bd0170famr7777207f8f.48.1725370377570; Tue, 03 Sep 2024 06:32:57 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Alexander Korotkov Date: Tue, 3 Sep 2024 16:32:46 +0300 Message-ID: Subject: Re: POC: make mxidoff 64 bits To: Maxim Orlov Cc: wenhui qiu , Heikki Linnakangas , Postgres hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Sep 3, 2024 at 4:30=E2=80=AFPM Maxim Orlov wrot= e: > Here is rebase. Apparently I'll have to do it often, since the CATALOG_V= ERSION_NO changed in the patch. I don't think you need to maintain CATALOG_VERSION_NO change in your patch for the exact reason you have mentioned: patch will get conflict each time CATALOG_VERSION_NO is advanced. It's responsibility of committer to advance CATALOG_VERSION_NO when needed. ------ Regards, Alexander Korotkov Supabase