From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Noah Misch <noah(at)leadboat(dot)com> |
Cc: | Matthew Gerber <gerber(dot)matthew(at)gmail(dot)com>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Unresolved error 0xC0000409 on Windows Server |
Date: | 2012-11-12 01:27:15 |
Message-ID: | 15685.1352683635@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Noah Misch <noah(at)leadboat(dot)com> writes:
> So, I can reproduce the lower threshold, but the exception type does not agree
> with the one Matthew observed.
I finally got around to looking at the link you provided about error
0xC0000409, and realized that I'd been completely confusing it with
stack overflow --- but actually, it's a report that something scribbled
past the end of a finite-size local-variable array. So I now think that
Matthew's stumbled across two completely independent bugs, and we've
fixed only one of them. The 0xC0000409 error is something else, and
possibly a lot worse since it could conceivably be a security issue.
It still seems likely that the actual location of the bug is either
in PostGIS or in the GIST index code, but without the ability to
reproduce the failure it's awfully hard to find it. Matthew, could
you try a bit harder to find a self-contained test case that produces
that error?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew Gerber | 2012-11-12 02:45:54 | Re: Unresolved error 0xC0000409 on Windows Server |
Previous Message | Andres Freund | 2012-11-12 01:12:47 | Re: Inadequate thought about buffer locking during hot standby replay |