From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: New strategies for freezing, advancing relfrozenxid early |
Date: | 2022-11-16 03:02:12 |
Message-ID: | CAH2-Wz=-7_epivYdWN9F899iKKfgQ+zj8Myi7ZwBqMVsegRNJQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 10, 2022 at 7:44 PM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
> performing post-bootstrap initialization ...
> ../src/backend/access/heap/visibilitymap.c:482:38: runtime error: load of misaligned address 0x5559e1352424 for type 'uint64', which requires 8 byte alignment
This issue is fixed in the attached revision, v6. I now avoid breaking
alignment-picky platforms in visibilitymap.c by using PGAlignedBlock
in the vm snapshot struct (this replaces the raw char buffer used in
earlier revisions).
Posting v6 will also keep CFTester happy. v5 no longer applies cleanly
due to conflicts caused by today's "Deduplicate freeze plans in freeze
WAL records" commit.
No other changes in v6 that are worth noting here.
Thanks
--
Peter Geoghegan
Attachment | Content-Type | Size |
---|---|---|
v6-0005-Avoid-allocating-MultiXacts-during-VACUUM.patch | application/x-patch | 6.8 KB |
v6-0004-Make-VACUUM-s-aggressive-behaviors-continuous.patch | application/x-patch | 98.1 KB |
v6-0001-Add-page-level-freezing-to-VACUUM.patch | application/x-patch | 27.7 KB |
v6-0003-Add-eager-freezing-strategy-to-VACUUM.patch | application/x-patch | 25.0 KB |
v6-0002-Teach-VACUUM-to-use-visibility-map-snapshot.patch | application/x-patch | 31.0 KB |
v6-0006-Size-VACUUM-s-dead_items-space-using-VM-snapshot.patch | application/x-patch | 4.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2022-11-16 03:10:50 | Re: SUBTRANS: Minimizing calls to SubTransSetParent() |
Previous Message | Julien Rouhaud | 2022-11-16 02:53:02 | Re: Allow file inclusion in pg_hba and pg_ident files |