| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Jeremy Finzel <finzelj(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Size estimation of postgres core files |
| Date: | 2019-02-15 18:27:02 |
| Message-ID: | 87d0nslxju.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>>>>> "Jeremy" == Jeremy Finzel <finzelj(at)gmail(dot)com> writes:
Jeremy> Yes Linux. This is very helpful, thanks. A follow-up question -
Jeremy> will it take postgres a really long time to crash (and
Jeremy> hopefully recover) if I have say 1T of RAM because it has to
Jeremy> write that all out to a core file first?
It doesn't write out all of RAM, only the amount in use by the
particular backend that crashed (plus all the shared segments attached
by that backend, including the main shared_buffers, unless you disable
that as previously mentioned).
And yes, it can take a long time to generate a large core file.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-02-15 18:31:41 | Re: Problems pushing down WHERE-clause to underlying view |
| Previous Message | Andre Piwoni | 2019-02-15 18:23:22 | Promoted slave tries to archive previously archived WAL file |