| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) |
| Date: | 2010-12-16 14:07:33 |
| Message-ID: | AANLkTikoXtZ5krsP_1c3TA-pxR-anfqPpN2mwydgaLut@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 16, 2010 at 8:01 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> We use the existance of the "crashdumps" directory as an indication we
> want crashdumps. That's fine when the system is up. But what if we
> crash *in the postmaster before we have done chdir()*?
>
> Should we perhaps instead define a subdirectory of *where the .EXE
> file is*, and dump the file there?
That seems pretty ugly, for a pretty marginal case. The number of
crashes that are going to happen in the postmaster before we've done
chdir() should be extremely small, especially if we're talking about
crashes in the field rather than during development. How about adding
a command-line option to force a dump to be written in $CWD whether a
crashdumps directory exists or not?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-12-16 14:08:39 | Re: Extensions, patch v18 (merge against master, bitrot-only-fixes) |
| Previous Message | Dimitri Fontaine | 2010-12-16 14:04:31 | Re: Extensions, patch v18 (merge against master, bitrot-only-fixes) |