Skip site navigation (1) Skip section navigation (2)

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 (view raw, whole thread or download thread mbox)
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            Sweden

In response to


pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group