From: Andres Freund <andres@anarazel.de>
To: Tomas Vondra <tv@fuzzy.cz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-committers <pgsql-committers@postgresql.org>
Cc: Andrew Dunstan <andrew@dunslane.net>
Subject: Re: pgsql: Generational memory allocator
Date: Thu, 23 Nov 2017 13:46:36 -0800
Message-ID: <20171123214636.unwkrkunr7m2bkii@alap3.anarazel.de> (raw)
In-Reply-To: <c09b1f12-8042-1e77-1b3e-ca68a2b44167@fuzzy.cz>
References: <E1eHa4J-0006hI-Q8@gemulon.postgresql.org>
<20171123001649.y2nf7422iay6cw3v@alap3.anarazel.de>
<CANP8+jKoT=Pg5W_3FcKiDf+FMrJhFYacxt_g5E0=tkmb5s8M6g@mail.gmail.com>
<20171123193936.fncfnar5wkpx56mw@alap3.anarazel.de>
<21043.1511467602@sss.pgh.pa.us>
<c09b1f12-8042-1e77-1b3e-ca68a2b44167@fuzzy.cz>
On 2017-11-23 22:34:57 +0100, Tomas Vondra wrote:
> > I think it's a legitimate complaint that postmaster.log wasn't captured
> > in this failure, but that's a buildfarm script oversight and hardly
> > Andres' fault.
> >
>
> Are the valgrind errors really written to postmaster log? I'm assuming it
> failed because valgrind ran into an issue and killed the process.
Yes. Search e.g. in
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skink&dt=2017-09-18%2004%3A10%3A01
for VALGRINDERROR-BEGIN.
(You could argue that they're only written there in certain
configurations, because I'd assume it'd not work in e.g. syslog
configured systems, because valgrind just prints to stderr).
> Hmmm, I see. Presumably adding this to GenerationChunk (similarly to what we
> do in AllocChunkData) would address the issue:
>
> #if MAXIMUM_ALIGNOF > 4 && SIZEOF_VOID_P == 4
> Size padding;
> #endif
>
> but I have no way to verify that (no access to such machine). I wonder why
> SlabChunk doesn't need to do that (perhaps a comment explaining that would
> be appropriate?).
Can't you just compile pg on a 32bit system and manually define MAXALIGN
to 8 bytes?
Greetings,
Andres Freund
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 using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: andres@anarazel.de, tv@fuzzy.cz, tgl@sss.pgh.pa.us, simon@2ndquadrant.com, andrew@dunslane.net
Subject: Re: pgsql: Generational memory allocator
In-Reply-To: <20171123214636.unwkrkunr7m2bkii@alap3.anarazel.de>
* 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