From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [Fwd: PGBuildfarm member narwhal Branch HEAD Status changed from OK to InstallCheck failure] |
Date: | 2007-04-22 21:27:16 |
Message-ID: | 462BD334.1080206@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Dave Page <dpage(at)postgresql(dot)org> writes:
>> Tom Lane wrote:
>>> If you want to poke at it, I'd suggest changing the ERROR to PANIC
>>> (it's in bufmgr.c) to cause a core dump, run installchecks till you
>>> get a panic, and then look around in the dump to see what you can find.
>>> It'd be particularly interesting to see what the buffer actually
>>> contains. Also you could look at the corresponding page of the disk
>>> file (which in theory should be the same as the buffer contents,
>>> since this error check is only made just after a read() ...)
>
>> Hmm, I'll give it a go when I'm back in the office, but bear in mind
>> this is a Mingw build on which debugging is nigh-on impossible.
>
> I was afraid of that. Well, at least get a dump of page 104 in that
> index so we can see what's on-disk.
Sure - I'll have to try with 8.1/8.2 unless you have a pg_filedump
that'll work with -HEAD?
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-04-22 21:36:14 | Re: [Fwd: PGBuildfarm member narwhal Branch HEAD Status changed from OK to InstallCheck failure] |
Previous Message | Kevin Grittner | 2007-04-22 20:35:02 | Please add EXISTS optimization to TODO list |