From: Robert Haas <rhaas@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix alignment problems with SharedInvalSmgrMsg.
Date: Wed, 28 Sep 2022 11:59:55 +0000
Message-ID: <E1odVjG-002Nvd-Th@gemulon.postgresql.org> (raw)
Fix alignment problems with SharedInvalSmgrMsg.
SharedInvalSmgrMsg can't require 8-byte alignment, because then
SharedInvalidationMessage will require 8-byte alignment, which will
then cause ParseCommitRecord to fail on machines that are picky
about alignment, because it assumes that everything that gets
packed into a commit record requires only 4-byte alignment.
Another problem with 05d4cbf9b6ba708858984b01ca0fc56d59d4ec7c.
Discussion: http://postgr.es/m/3825454.1664310917@sss.pgh.pa.us
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/0222be137188ac3912d244d832a328be0944f3e9
Modified Files
--------------
src/backend/utils/cache/inval.c | 9 +++++++--
src/include/storage/sinval.h | 7 +++++--
2 files changed, 12 insertions(+), 4 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: rhaas@postgresql.org
Subject: Re: pgsql: Fix alignment problems with SharedInvalSmgrMsg.
In-Reply-To: <E1odVjG-002Nvd-Th@gemulon.postgresql.org>
References: <E1odVjG-002Nvd-Th@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox