From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: Dmitry Dolgov <9erthalion6@gmail.com>,
        Michael Paquier <michael.paquier@gmail.com>,
        Vincent Lachenal <vincent.lachenal@gmail.com>,
        PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Subject: Re: BUG #14897: Segfault on statitics SQL request
In-reply-to: <20171111171620.td6vtnmijcloj6k5@alap3.anarazel.de>
References: 
 <CAA2tJ7odG4KB=wvu_+5FfssxckbLTnEuR9C_TXRyeU_35z+CSA@mail.gmail.com>
 <10197.1510349123@sss.pgh.pa.us>
 <CAA2tJ7p72wbuHEzOA_g2V4YcmeDPHYKggenTR4dXG=kSpCiO8Q@mail.gmail.com>
 <14075.1510352167@sss.pgh.pa.us>
 <CA+q6zcXe9aV5NV88u9Y=vMp+=fP7QOXgTyFQhzuvmCvTBvb_kQ@mail.gmail.com>
 <17617.1510355215@sss.pgh.pa.us>
 <CAB7nPqR7mWvtnALZF93oez_v03NFCJ8dXP9CNicaUDv3KjDbYw@mail.gmail.com>
 <CA+q6zcVE2FQ9irhENEy=2WjRWgV2hyzfYyOXFs36w=hsk4faBw@mail.gmail.com>
 <644.1510418216@sss.pgh.pa.us>
 <CA+q6zcWwjTNgA6JiqQ5L-oAFF5X9ONtKSAvznte63A7Zb7zaww@mail.gmail.com>
 <20171111171620.td6vtnmijcloj6k5@alap3.anarazel.de>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Sat, 11 Nov 2017 09:16:20 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3913.1510422100.1@sss.pgh.pa.us>
Date: Sat, 11 Nov 2017 12:41:40 -0500
Message-ID: <3914.1510422100@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

Andres Freund <andres@anarazel.de> writes:
> That's using SSE, which requires 16byte alignment IIRC.  I think we need
> a function that properly allocate int128 vars with the right alignment -
> don't think we want to go for full 16byte alignment for everything.

Yeah, changing MAXALIGN is out of the question.  I'm thinking about
another flag bit for MemoryContextAllocExtended.  Do we need to think
about other use-cases besides int128?  Should we just force 16-byte
alignment on all architectures, or does it need to be platform-specific?

			regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs