| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) |
| Date: | 2010-12-19 16:02:48 |
| Message-ID: | 24439.1292774568@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Sun, Dec 19, 2010 at 07:26, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> wrote:
>> fcinfo->flinfo is still inaccessible, but I suspect it's in shared memory,
>> as it's at 0x00000135 . Ditto fcinfo->resultinfo and fcinfo->context.
> Hmm. Not sure why those would be in shared memory, that seems strange.
FWIW, I don't believe that theory either. Offhand I cannot think of any
case where an FmgrInfo would be in shared memory. It seems more likely
from the above that you've misidentified where the fcinfo record is.
There are some code paths where we don't bother to set up those fields,
but I think we're always careful to set them to NULL if so.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-12-19 16:07:25 | Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) |
| Previous Message | Robert Haas | 2010-12-19 16:01:08 | Re: serializable lock consistency |