| From: | Richard Frith-Macdonald <richardfrithmacdonald(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Elusive segfault with 9.3.5 & query cancel |
| Date: | 2014-12-05 23:02:55 |
| Message-ID: | FC62C0A8-CF57-45F7-960A-D74422E20736@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5 Dec 2014, at 22:41, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>
>
> Perhaps we should also officially recommend production servers be setup to create core files. AFAIK the only downside is the time it would take to write a core that's huge because of shared buffers, but perhaps there's some way to avoid writing those? (That means the core won't help if the bug is due to something in a buffer, but that seems unlikely enough that the tradeoff is worth it...)
Good idea. It seems the madvise() system call (with MADV_DONTDUMP) is exactly what's needed to avoid dumping shared buffers.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-12-05 23:23:37 | Re: Elusive segfault with 9.3.5 & query cancel |
| Previous Message | Peter Geoghegan | 2014-12-05 22:54:06 | Re: Elusive segfault with 9.3.5 & query cancel |