Re: Is *that* why debugging backend startup is so hard!?

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Is *that* why debugging backend startup is so hard!?
Date: 2000-06-27 18:11:59
Message-ID: Pine.LNX.4.21.0006272010040.7809-100000@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-06-27 18:18:07 Re: Big 7.1 open items
Previous Message Bruce Momjian 2000-06-27 18:08:05 Re: [HACKERS] Re: Call for port testing on fmgr changes -- Results!