| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | Re: 64-bit XIDs in deleted nbtree pages |
| Date: | 2021-02-10 07:08:33 |
| Message-ID: | CAH2-WzkgtJ6RvyyHbMPHDNGiLwGEYzNFFmwGNLh5S6G8EdT1VA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 9, 2021 at 5:53 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Here is a plan that allows us to stop storing any kind of XID in the
> metapage in all cases:
Attached is v2, which deals with the metapage 32-bit
XID/btm_oldest_btpo_xact issue using the approach I described earlier.
We don't store an XID in the metapage anymore in v2. This seems to
work well, as I expected it would.
--
Peter Geoghegan
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Use-full-64-bit-XID-for-nbtree-page-deletion.patch | application/octet-stream | 64.5 KB |
| v2-0002-Add-pages_newly_deleted-to-VACUUM-VERBOSE.patch | application/octet-stream | 13.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-02-10 07:11:52 | Re: New IndexAM API controlling index vacuum strategies |
| Previous Message | tsunakawa.takay@fujitsu.com | 2021-02-10 06:59:59 | RE: Parallel INSERT (INTO ... SELECT ...) |