| From: | Maarten Boekhold <maartenb(at)dutepp0(dot)et(dot)tudelft(dot)nl> |
|---|---|
| To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>, brett(at)work(dot)chicken(dot)org, pgsql-hackers(at)hub(dot)org, "Marc G(dot) Fournier" <scrappy(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] dec alpha/64bit stuff |
| Date: | 1998-03-08 10:40:52 |
| Message-ID: | Pine.SUN.3.91.980308114008.21122A-100000@dutepp0.et.tudelft.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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.
Another suggestion: use a binary search to find the date it broke. Will
save you a lot of time :)
Maarten
_____________________________________________________________________________
| TU Delft, The Netherlands, Faculty of Information Technology and Systems |
| Department of Electrical Engineering |
| Computer Architecture and Digital Technique section |
| M(dot)Boekhold(at)et(dot)tudelft(dot)nl |
-----------------------------------------------------------------------------
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter T Mount | 1998-03-08 11:09:03 | Re: WG: [QUESTIONS] Re: [HACKERS] text should be a blob field |
| Previous Message | Herouth Maoz | 1998-03-08 09:44:15 | Re: [QUESTIONS] Testing Postgresql v6.3 |