| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Maxim Orlov <orlovmg(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com> |
| Cc: | Zhang Mingli <zmlpostgres(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Pavel Borisov <pashkin(dot)elfe(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Stephen Frost <sfrost(at)snowman(dot)net>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Ilya Anfimov <ilan(at)tzirechnoy(dot)com> |
| Subject: | Re: Add 64-bit XIDs into PostgreSQL 15 |
| Date: | 2022-11-21 19:05:04 |
| Message-ID: | 21fc23b4-c47f-959f-9123-a0f25f0f458d@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-11-21 19:09:52 | Re: Damage control for planner's get_actual_variable_endpoint() runaway |
| Previous Message | sirisha chamarthi | 2022-11-21 19:02:45 | Re: Catalog_xmin is not advanced when a logical slot is lost |