On Thu, Dec 16, 2010 at 15:07, Robert Haas <robertmh...@gmail.com> wrote: > On Thu, Dec 16, 2010 at 8:01 AM, Magnus Hagander <mag...@hagander.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?
Is that less ugly? ;) But yes, we are talking about in the field, so it's fairly small. But any crash during guc loading for example would go there, I think? We can do such a commandline. We don't have any platform-specific commandline options today. Is that something we've intentionally avoided, or just not needed before? -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
