Skip site navigation (1) Skip section navigation (2)

Re: sudden program termination: no warning, error, or crash

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Rainer Bauer <usenet(at)munnin(dot)com>
Cc: pgadmin-support(at)postgresql(dot)org, JwexlerAt MailDotCom <jwexler(at)mail(dot)usa(dot)com>
Subject: Re: sudden program termination: no warning, error, or crash
Date: 2009-08-17 10:26:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-support
On Thu, Aug 13, 2009 at 8:45 AM, Rainer Bauer<usenet(at)munnin(dot)com> wrote:
> Hello,
> Thursday, August 13, 2009, 2:38:02 AM, you wrote:
> JM> I am also getting repeated sudden program terminations. My
> JM> environment is Windows Server 2003 Native Japanese OS. Postgresql
> JM> 8.4. Pgadmin III 1.10. Often after just having added a column, the
> JM> program terminates. In all cases thus far, the operation that I
> JM> was performing (addition to or maintenance of a column) was
> JM> successful (i.e., the change was saved).
> Although this won't be helpful, but it happened to me as well
> yesterday. WinXPSP3 pgAdmin1.10 connected to a PostgreSQL 8.4
> database.
> I was left clicking on group/user roles in the tree view when pgAdmin
> crashed and the window disappeared.
> After restarting the program I tried to reproduce this behaviour, but
> the crash was not reproducable.

I'm not sure how we'll be able to track down these cases without a
reproducible test case. That said, I've been fixing some bugs that
cause similar crashes on Solaris which seems to be *far* more picky
about some things than other OSs. From the description that jwexler
gave, it's not beyond the realms of possibility that you are seeing
the same/similar bugs, just with far less frequency.

Dave Page
EnterpriseDB UK:

In response to


pgadmin-support by date

Next:From: David SchnurDate: 2009-08-18 18:16:26
Subject: Saving window maximize state
Previous:From: Dave PageDate: 2009-08-17 10:22:41
Subject: Re: Feature request: Reget oid of tables/views when doing a reload

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group