On Tue, 30 Aug 2022 at 03:39, Tom Lane <t...@sss.pgh.pa.us> wrote: > I'd suggest reverting df0f4feef as it seems to be > a red herring.
I think it's useless providing that a 64-bit variable will always be aligned to 8 bytes on all of our supported 32-bit platforms as, without the padding, the uint64 hdrmask in MemoryChunk will always be aligned to 8 bytes meaning the memory following that will be aligned too. If we have a platform where a uint64 isn't aligned to 8 bytes then we might need the padding. long long seems to align to 8 bytes on my 32-bit Rasberry PI going the struct being 16 bytes rather than 12. drowley@raspberrypi:~ $ cat struct.c #include <stdio.h> typedef struct test { int a; long long b; } test; int main(void) { printf("%d\n", sizeof(test)); return 0; } drowley@raspberrypi:~ $ gcc struct.c -o struct drowley@raspberrypi:~ $ ./struct 16 drowley@raspberrypi:~ $ uname -m armv7l Is that the case for your 32-bit PPC too? David