On Sat, 7 March 1998, at 18:10:36, Bruce Momjian wrote:
> OK, I have an idea. Contact Marc, scrappy@postgresql.org. Have him
> give you a login account to postgresql.org. Use cvs to pull snapshots
> by date. Compile and run initdb on several dates, and by process of
> elimination, find out the day that alpha broke.
That's what I've been thinking of, but I haven't had a chance to get
the cvs archive yet.
>
> We can then analyze the patches for that day and find the problem. I
> assume 6.2.1 worked for you, and that was October 17th. Go from there
> to the 6.3 release and find the date of failure.
>
> With initdb problems, there is really no good way to debug problems like
> this.
I found a decent way. I just put a printf(getpid()), sleep 10 in
BootstrapMain. Then I run initdb in one window and gdb in another,
attaching gdb to that postgres -boot process. Worked fairly well
until I got stumped by the page stuff.
