Re: Is *that* why debugging backend startup is so hard!? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Is *that* why debugging backend startup is so hard!?
Date
Msg-id Pine.LNX.4.21.0006272010040.7809-100000@localhost.localdomain
Whole thread Raw
In response to Is *that* why debugging backend startup is so hard!?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Is *that* why debugging backend startup is so hard!?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane writes:

> I just spent a rather frustrating hour trying to debug a backend startup
> failure --- and getting nowhere because I couldn't catch the failure in
> a debugger, or even step to where I thought it might be.  I've seen this
> sort of difficulty before, and always had to resort to expedients like
> putting in printf's.  But tonight I finally realized what the problem is.

Could that be contributing to the Heisenbug I decribed on Sunday in "Pid
file magically disappears"?


-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-hackers by date:

Previous
From: "Mikheev, Vadim"
Date:
Subject: RE: Big 7.1 open items
Next
From: Bruce Momjian
Date:
Subject: Re: Re: Call for port testing on fmgr changes -- Results!