aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw/postgres_fdw.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2017-08-16 21:52:38 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2017-08-16 21:52:38 +0300
commitac883ac453e9c479f397780918f235c440b7a02f (patch)
treeaaaccbaee521dd6e67d055c1654d26f3fdea9c07 /contrib/postgres_fdw/postgres_fdw.c
parent4395f7daf3b40ecbd316bd2a68c253a56013a538 (diff)
downloadpostgresql-ac883ac453e9c479f397780918f235c440b7a02f.tar.gz
postgresql-ac883ac453e9c479f397780918f235c440b7a02f.zip
Fix shm_toc.c to always return buffer-aligned memory.
Previously, if you passed a non-aligned size to shm_toc_create(), the memory returned by shm_toc_allocate() would be similarly non-aligned. This was exposed by commit 3cda10f41b, which allocated structs containing a pg_atomic_uint64 field with shm_toc_allocate(). On systems with MAXIMUM_ALIGNOF = 4, such structs still need to be 8-bytes aligned, but the memory returned by shm_toc_allocate() was only 4-bytes aligned. It's quite bogus that we abuse BUFFERALIGN to align the structs for pg_atomic_uint64. It doesn't really have anything to do with buffers. But that's a separate issue. This ought to fix the buildfarm failures on 32-bit x86 systems. Discussion: https://www.postgresql.org/message-id/7e0a73a5-0df9-1859-b8ae-9acf122dc38d@iki.fi
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions