Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)
Date
Msg-id 10775.1290451186@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Mon, Nov 22, 2010 at 18:46, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> ... I haven't looked at the patch but this
>> discussion makes it sound like the dumper is dependent on an
>> uncomfortably large amount of backend code being functional.

> No, it's dependent on close to zero backend functionality.
> Particularly if we take out the dependency on elog() (write_stderr is
> much simpler). In fact, the calls to elog() are the *only* places
> where it calls into the backend as it stands today.

Well, in the contrib-module guise, it's dependent on
shared_preload_libraries or local_preload_libraries, which at least
involves guc and dfmgr working pretty well (and not only in the
postmaster, but during backend startup).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)
Next
From: Magnus Hagander
Date:
Subject: Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)