Dave Page wrote:
> On Tue, Aug 31, 2010 at 4:27 PM, Bruce Momjian <bruce@momjian.us> wrote:
> > Dave Page wrote:
> >> On Tue, Aug 31, 2010 at 3:40 PM, Cristian Bittel <cbittel@gmail.com> wrote:
> >> > To Dave's question, this behavior occurs on all Windows Server interactive
> >> > sessions, no matter if Administrators or underpriviledge users, but is
> >> > related to closing Windows interactive session while pgAdmin window is
> >> > opened and connected to service. Nobody logon to Windows using "postgres"
> >> > service user.
> >>
> >> Thanks Cristian.
> >>
> >> Can you reproduce the problem if you use psql instead of pgAdmin? Both
> >> use libpq to talk to the server, so if your theory is correct, I would
> >> expect to see the same crash. It's hard to see what would bring the
> >> server down though...
> >
> > We have already found that exceeding desktop heap might cause a
> > CreateProcess to return success but later fail with a return code of
> > 128, which causes a server restart.
>
> That doesn't mean that this is desktop heap exhaustion though - just
> that it can cause the same effect.
Right, but it is the only possible server crash cause we have come up
with so far.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ It's impossible for everything to be true. +