| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jakub Glapa <jakub(dot)glapa(at)gmail(dot)com> |
| Cc: | pryzby(at)telsasoft(dot)com, pgsql-performance(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Subject: | Re: dsa_allocate() faliure |
| Date: | 2018-11-26 18:45:09 |
| Message-ID: | 20181126184509.gge2vqmlu3twf72h@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On 2018-Nov-26, Jakub Glapa wrote:
> Justin thanks for the information!
> I'm running Ubuntu 16.04.
> I'll try to prepare for the next crash.
> Couldn't find anything this time.
As I recall, the appport stuff in Ubuntu is terrible ... I've seen it
take 40 minutes to write the crash dump to disk, during which the
database was "down". I don't know why it is so slow (it's a rather
silly python script that apparently processes the core dump one byte at
a time, and you can imagine that with a few gigabytes of shared memory
that takes a while). Anyway my recommendation was to *remove* that
stuff from the server and make sure the core file is saved by normal
means.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2018-11-26 18:46:28 | Re: Copy function for logical replication slots |
| Previous Message | Sergei Kornilov | 2018-11-26 18:34:38 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-11-27 03:00:34 | Re: dsa_allocate() faliure |
| Previous Message | Tom Lane | 2018-11-26 16:10:33 | Re: autovacuum run but last_autovacuum is empty |