| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
| Cc: | 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:21:13 |
| Message-ID: | 2880.1510420873@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Dmitry Dolgov <9erthalion6(at)gmail(dot)com> writes:
>> On 11 November 2017 at 17:36, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Would you guys who are seeing the problem note whether the address of
>> the int128 field is 16-aligned, or only 8-aligned?
> __alignof__(__int128) returns 16 on my machine.
The question was about the actual value of the pointer being used at
the time of the crash --- %rax in the example below.
> Here is the disassembly section I've got in my case:
> 0x00000000007fc47d numericvar_to_int128+467 movdqa -0x60(%rbp),%xmm0
> --> 0x00000000007fc482 numericvar_to_int128+472 movaps %xmm0,(%rax)
suspicious ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-11-11 17:41:40 | Re: BUG #14897: Segfault on statitics SQL request |
| Previous Message | Andres Freund | 2017-11-11 17:16:20 | Re: BUG #14897: Segfault on statitics SQL request |