From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
cc: Maxim Orlov <orlovmg@gmail.com>, Thom Brown <thom@linux.com>,
        Zhang Mingli <zmlpostgres@gmail.com>,
        Michael Paquier <michael@paquier.xyz>,
        Justin Pryzby <pryzby@telsasoft.com>,
        Dilip Kumar <dilipbalaut@gmail.com>,
        Pavel Borisov <pashkin.elfe@gmail.com>,
        Aleksander Alekseev <aleksander@timescale.com>,
        pgsql-hackers@lists.postgresql.org,
 Stephen Frost <sfrost@snowman.net>,
        Alexander Korotkov <aekorotkov@gmail.com>,
        Andres Freund <andres@anarazel.de>, Ilya Anfimov <ilan@tzirechnoy.com>
Subject: Re: Add 64-bit XIDs into PostgreSQL 15
In-reply-to: <21fc23b4-c47f-959f-9123-a0f25f0f458d@enterprisedb.com>
References: 
 <CAJ7c6TPHBwU87+oRdTUHVy7bKNnCfZPywJJBKuUhUcNQQ3xUaw@mail.gmail.com>
 <CALT9ZEHiPQJn8GjZpjfCJTNg-fD+innHxTCEH-CX=zYyH81=sw@mail.gmail.com>
 <CAFiTN-s6=M3hHo_Rjic8WvHJe=-m+vc3aa4uQwh2pLFkHR8XJQ@mail.gmail.com>
 <CAFiTN-vZ26KdkBzE1xwJqi0E6y87HH_m-od54fq1FfirTmG+9A@mail.gmail.com>
 <CACG=ezZUhMiBSrjj4ZhxXyaoOP3zf-YVAh+0UK7YhOQ=N88efw@mail.gmail.com>
 <CACG=ezaSke1CJrbG110RwiqTF-Dw0H8nqhwGVd1eMCB369yhZw@mail.gmail.com>
 <d90f891e-548a-4477-bf8c-b7b038b8db52@Spark>
 <20220920092643.GB31833@telsasoft.com>
 <a6e43cab-375f-4a32-abcf-398ae7a9720c@Spark>
 <CACG=ezYt4qJpV3PxvpVD2AtEBE-dwnibD=2pfnAwHTD89xefrw@mail.gmail.com>
 <Y0ZuqGHdzn9aUD2y@paquier.xyz>
 <CACG=ezZSx2UNhaSyV9DPWfHK230E2_Rg87Uef8KHokRsAE_Wfw@mail.gmail.com>
 <f4e0435e-9540-42df-b81c-7f3ae38655c0@Spark>
 <CACG=ezaR-b=oHriU5y0NH5B7TrOjy_kb3N_3aQv=PcHeToREPw@mail.gmail.com>
 <CAA-aLv66OSmjqebjfjPS2hwm4UYc48iO_kHyALQPV0CWuR85+Q@mail.gmail.com>
 <CACG=ezYiRfkNb3dTqeThebRL3mVfMm65hqaXOuk=FOGB_HbgQg@mail.gmail.com>
 <21fc23b4-c47!
 f-959f-9123-a0f25f0f458d@enterprisedb.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@enterprisedb.com>
	message dated "Mon, 21 Nov 2022 20:05:04 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3259163.1669058495.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 21 Nov 2022 14:21:35 -0500
Message-ID: <3259164.1669058495@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3259164.1669058495%40sss.pgh.pa.us>
Precedence: bulk

Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>> To date testing database cluster wraparund was not easy as initdb has a=
lways
>> 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?

pg_resetwal does seem like a better, more useful home for this; it'd
allow you to adjust these numbers after initial creation which might be
useful.  I'm not sure how flexible it is right now in terms of where
you can set the new values, but that can always be improved.

			regards, tom lane