From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
Cc: | brett(at)work(dot)chicken(dot)org, pgsql-hackers(at)hub(dot)org, scrappy(at)postgreSQL(dot)org (Marc G(dot) Fournier) |
Subject: | Re: [HACKERS] dec alpha/64bit stuff |
Date: | 1998-03-07 23:10:36 |
Message-ID: | 199803072310.SAA02877@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> Brett McCormick wrote:
>
> > whew.. after some more debugging, it would appear that the problem
> > lies somewhere in the page stuff, which I know less than nothing
> > about.
> >
> > Here's the point where I'm at: heapam.c line 442 a macro call to
> > HeapTupleSatisfies graps our data for us (the messed up struct), which
> > actually calls the PageGetItem macro for the data.
OK, I have an idea. Contact Marc, scrappy(at)postgresql(dot)org(dot) 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.
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.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
From | Date | Subject | |
---|---|---|---|
Next Message | Roland B. Roberts | 1998-03-08 03:59:01 | Re: [HACKERS] Re: your mail |
Previous Message | Bruce Momjian | 1998-03-07 21:16:29 | Re: [HACKERS] Backend crashes on select ... union |