On 02/27/2017 06:40 PM, Andres Freund wrote:
On 2017-02-27 18:04:41 +0100, Petr Jelinek wrote:
On 27/02/17 18:00, Andres Freund wrote:
FWIW I think the ppc64 machines are failing because of unrelated issue
(changes to integer timestamps). We should probably look at 32bit machines
first.
Don't think so - termite is ppc64 afaics, and the failure doesn't look
integer timestamp related (assert failure is clearly about this, and set
of changed commits *only* include slab related commits).
termite is ppc64 but with 4 byte pointer size according to configure so
it might be related to that perhaps?
Uh, ok. I checked the --configure options, but not the actual configure
output (blame -ENOCOFEE and jetlag). The output makes it fairly likely
that my StandardChunkHeader theory is valid, so I'll work on a patch to
clean that up.
Thanks. I set up a rpi3 machine (amrv7l) that fails with the same issue,
so if you need to test the patch, let me know.
While building, I've also noticed a bunch of warnings about string
formatting, attached is a patch that that fixes those.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
diff --git a/src/backend/utils/mmgr/slab.c b/src/backend/utils/mmgr/slab.c
index a5e140e..c673bc3 100644
--- a/src/backend/utils/mmgr/slab.c
+++ b/src/backend/utils/mmgr/slab.c
@@ -207,7 +207,7 @@ SlabContextCreate(MemoryContext parent,
/* Make sure the block can store at least one chunk. */
if (blockSize - sizeof(SlabBlock) < fullChunkSize)
- elog(ERROR, "block size %ld for slab is too small for %ld chunks",
+ elog(ERROR, "block size %zu for slab is too small for %zu chunks",
blockSize, chunkSize);
/* Compute maximum number of chunks per block */
@@ -333,7 +333,7 @@ SlabAlloc(MemoryContext context, Size size)
/* make sure we only allow correct request size */
if (size != slab->chunkSize)
- elog(ERROR, "unexpected alloc chunk size %ld (expected %ld)",
+ elog(ERROR, "unexpected alloc chunk size %zu (expected %zu)",
size, slab->chunkSize);
/*
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
