| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | Nailah Ogeer <ogeer(at)cs(dot)queensu(dot)ca>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Testing patches |
| Date: | 2003-05-26 06:28:02 |
| Message-ID: | 25903.1053930482@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> I've suffered from this pain before. The only thing that I have been
> able to do is run the initdb script by hand until the point of the
> crash, and then run the exact commands in postgres.bki using a
> standalone backend under a debugger. Believe me, it's not a
> particularly nice task. But I haven't found another way.
The initdb environment isn't particularly debugger-friendly. It'd seem
to me that bufmgr/relcache changes shouldn't impact the on-disk data
layout, and therefore could be tested and debugged in an already-created
installation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guido van Rossum | 2003-05-26 06:46:20 | Re: Expect problems with PL/Python and Python version 2.2.3+ |
| Previous Message | Tom Lane | 2003-05-26 06:22:54 | Re: Testing patches |