Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oxC6W-0001oJ-0d for pgsql-hackers@arkaria.postgresql.org; Mon, 21 Nov 2022 19:05:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oxC6U-0003lH-Rq for pgsql-hackers@arkaria.postgresql.org; Mon, 21 Nov 2022 19:05:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oxC6U-0003l8-Hf for pgsql-hackers@lists.postgresql.org; Mon, 21 Nov 2022 19:05:14 +0000 Received: from wout5-smtp.messagingengine.com ([64.147.123.21]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oxC6R-0007bN-Iu for pgsql-hackers@lists.postgresql.org; Mon, 21 Nov 2022 19:05:13 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id ACE1832009E4; Mon, 21 Nov 2022 14:05:08 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 21 Nov 2022 14:05:09 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1669057508; x= 1669143908; bh=26j/Z39M2555PHdskdhPWcttfeOo2m9d69vaJBY1jNY=; b=a UoDdi5JtILJ4+cx+YO0JTs4M9uibDz6dWuO2JNCaPFK30UMrB2LnDdRmzxJ+vO/F 70eoXrmYRGL/cx4E5Ffydyk3W70HtUHHSq/TDWXP7AeugHtiLxOLcC//7X+fbUqn VIgG4y2pXjh2Qss0mb3LzJYy1AAznBga0mzYL+wqA9ZLMqPaGzoBBg3NMDzQRnMc V1Qh/rAT0He0hDwbs9SfXEcfSJ4EOk/BM09RpKnRMzsMi8ssz1P5P6kU4vRGZVF1 JJdNlEXjgxu9LDqttaDX/DZcX69PyYXw9x1L/FNcv7ZuaRDyVUlmVJXQ3vEeTYAJ EInvqlL/P9N5t55fy5sQg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrheeigdduudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeehleffgeegudejteei hfelteduvdeifffhffdvjedvffegjeekudeludehudeifeenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 21 Nov 2022 14:05:05 -0500 (EST) Message-ID: <21fc23b4-c47f-959f-9123-a0f25f0f458d@enterprisedb.com> Date: Mon, 21 Nov 2022 20:05:04 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: Add 64-bit XIDs into PostgreSQL 15 Content-Language: en-US To: Maxim Orlov , Thom Brown Cc: Zhang Mingli , Michael Paquier , Justin Pryzby , Dilip Kumar , Pavel Borisov , Aleksander Alekseev , pgsql-hackers@lists.postgresql.org, Stephen Frost , Alexander Korotkov , Andres Freund , Ilya Anfimov References: <20220920092643.GB31833@telsasoft.com> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Question about """ Subject: [PATCH v50 5/8] Add initdb option to initialize cluster with non-standard xid/mxid/mxoff. To date testing database cluster wraparund was not easy as initdb has always inited it with default xid/mxid/mxoff. The option to specify any valid xid/mxid/mxoff at cluster startup will make these things easier. """ Doesn't pg_resetwal already provide that functionality, or at least some of it?