Re: BUG #16033: segmentation fault when runing update

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Miha Vrhovnik <miha(dot)vrhovnik(at)naviter(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16033: segmentation fault when runing update
Date: 2019-10-02 16:15:04
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

Miha Vrhovnik <miha(dot)vrhovnik(at)naviter(dot)com> writes:
> Unfortunately I'd need a bit of hand holding for generating a core as
> I've added the `ulimit -c unlimited` at the top of the init.d file but
> to no avail.

That seems reasonable. (Just to check off the obvious, you did
restart the postmaster service afterwards, right?)

> find / -name core

There are few if any modern platforms on which the name of a core
file is just "core" -- most people add a PID, for instance.
Searching the whole filesystem is also unlikely to be productive.
I'd just take a look into the PG data directory and see if you
see anything including "core" in its name.

Also, I don't know much about Ubuntu, but if it uses systemd then
probably systemd has commandeered collection of core files and
you need to negotiate with systemd-coredump. (Your reference to
an init.d file makes this theory unlikely, but I mention it
for completeness.)

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-10-02 16:51:47 Re: BUG #16034: `\set ECHO all` doesn't work for \e command
Previous Message Pavlo Golub 2019-10-02 16:11:39 Re: BUG #16034: `\set ECHO all` doesn't work for \e command