Hi I just checked the dmesg. The segfault I wrote about is the only one I see, dated Nov 24 last year. Since then no other segfaults happened although dsa_allocated failures happen daily. I'll report if anything occurs. I have the core dumping setup in place.
-- regards, pozdrawiam, Jakub Glapa On Sun, Feb 17, 2019 at 11:21 PM Justin Pryzby <pry...@telsasoft.com> wrote: > 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 >
