Richard Broersma wrote:
> Here is what the logs show:
>
> 2011-05-09 07:49:37 PDT LOG: server process (PID 2848) was terminated
> by exception 0xC0000005
>
Too bad, that's just a generic "accessed memory you shouldn't have"
exception. Not much help narrowing down the source. That could be a
driver or hardware issue, but since you say it's repeatable that seems
less likely.
At this point, fork in the road. If someone else can reproduce this on
another Windows system, they may be able to run with it. But if you can
spare some time to dig further, the instructions at
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
go over how to trace into where it's actually failing at yourself. If
you run PostgreSQL on Windows, that's good defensive practice to fit in
on a day it's not an emergency to do so. (The same is true of any
platform, it just takes more time to setup on Windows)
--
Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
