| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Vincent Lachenal <vincent(dot)lachenal(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14897: Segfault on statitics SQL request |
| Date: | 2017-11-11 17:41:40 |
| Message-ID: | 3914.1510422100@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-11-11 17:45:12 | Re: BUG #14897: Segfault on statitics SQL request |
| Previous Message | Tom Lane | 2017-11-11 17:21:13 | Re: BUG #14897: Segfault on statitics SQL request |