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

From Magnus Hagander
Subject Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)
Date
Msg-id AANLkTim_XnmVY8kGU96p3nzWcF_4OLDTv5U0-SBOOyJy@mail.gmail.com
Whole thread Raw
In response to Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Nov 22, 2010 at 19:39, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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).

Yes, sorry. My mindset was in "the version that'll go into 9.1".


--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)
Next
From: Peter Eisentraut
Date:
Subject: Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)