| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Lars Aksel Opsahl <Lars(dot)Opsahl(at)nibio(dot)no> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: free(): invalid pointer , when to dumping data to a new server |
| Date: | 2020-10-27 16:04:59 |
| Message-ID: | 1058472.1603814699@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Lars Aksel Opsahl <Lars(dot)Opsahl(at)nibio(dot)no> writes:
> Here is the new stackstrace not too much info that helps mee thou.
This is probably the reason why "bt" is producing garbage:
> BFD: warning: /var/lib/systemd/coredump/core.postmaster.26.6f7d98107f544085a41c6f8b876418d0.298120.1603810048000000 is truncated: expected core file size >= 2326896640, found: 2147483648
So the core file is being truncated at 2GB, but the process image was a
little bit larger than that. You need to get a complete core file.
First thing I'd check is the "ulimit -c" setting that the postmaster is
being started under. I see that systemd is capturing the core dump,
so it could also be that there's some systemd configuration you need
to adjust ("man systemd-coredump" might help here).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lars Aksel Opsahl | 2020-10-27 16:43:14 | Re: free(): invalid pointer , when to dumping data to a new server |
| Previous Message | Alvaro Herrera | 2020-10-27 16:04:35 | Re: free(): invalid pointer , when to dumping data to a new server |