| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeremy Finzel <finzelj(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Size estimation of postgres core files |
| Date: | 2019-02-15 16:36:55 |
| Message-ID: | 20190215163655.GA16325@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2019-Feb-15, Jeremy Finzel wrote:
> I am trying to determine the upper size limit of a core file generated for
> any given cluster. Is it feasible that it could actually be the entire
> size of the system memory + shared buffers (i.e. really huge)?
In Linux, yes. Not sure about other OSes.
You can turn off the dumping of shared memory with some unusably
unfriendly bitwise arithmetic using the "coredump_filter" file in /proc
for the process. (It's inherited by children, so you can just set it
once for postmaster at server start time).
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-02-15 17:06:58 | Re: WSL (windows subsystem on linux) users will need to turn fsync off as of 11.2 |
| Previous Message | Jeremy Finzel | 2019-02-15 16:33:48 | Size estimation of postgres core files |