| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Jakub Glapa <jakub(dot)glapa(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Subject: | Re: dsa_allocate() faliure |
| Date: | 2019-02-17 22:21:29 |
| Message-ID: | 20190217222129.GE28750@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Hi,
On Mon, Nov 26, 2018 at 09:52:07AM -0600, Justin Pryzby wrote:
> Hi, thanks for following through.
>
> On Mon, Nov 26, 2018 at 04:38:35PM +0100, Jakub Glapa wrote:
> > I had a look at dmesg and indeed I see something like:
> >
> > postgres[30667]: segfault at 0 ip 0000557834264b16 sp 00007ffc2ce1e030
> > error 4 in postgres[557833db7000+6d5000]
>
> That's useful, I think "at 0" means a null pointer dereferenced.
Thomas fixed several bugs in DSA, which will be in next release, postgres 10.8
and 11.3.
However that doesn't explain the segfault you saw, and I don't see anything
which looks relevant changed since in 10.5.
If you still see that using the latest minor release (10.7), please try to
capture a core file and send a backtrace with a new thread on pgsql-hackers.
Thanks,
Justin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2019-02-17 22:22:03 | Re: Ryu floating point output patch |
| Previous Message | David Rowley | 2019-02-17 22:17:52 | Re: BUG #15572: Misleading message reported by "Drop function operation" on DB with functions having same name |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jakub Glapa | 2019-02-18 09:11:10 | Re: dsa_allocate() faliure |
| Previous Message | Tom Lane | 2019-02-16 22:37:49 | Re: Performance regressions found using sqlfuzz |