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

Re: BUG #5305: Postgres service stops when closing Windows session

From: Chris Travers <chris(at)metatrontech(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Cristian Bittel <cbittel(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5305: Postgres service stops when closing Windows session
Date: 2010-02-07 01:09:24
Message-ID: 5ed37b141002061709s1a2451e8lf56588328918d388@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
On Sat, Feb 6, 2010 at 2:36 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

>
> That's really odd.  Nothing pgAdmin does should be able to crash the
> PostgreSQL server, I would think.  Have you got any custom code loaded
> into PostgreSQL?  Or non-custom, but buggy?
>
> I'm guessing the problem only occurs if PGadmin is actually connected
> to the PostgreSQL server, but perhaps you could verify that.  If so, I
> would see if you can get a stack backtrace of the backend to which
> PGadmin is connected.

It wouldn't surprise me if this were a Windows bug (Terminal Services
may have improved since I was supporting it but it used to be quite
common that it would cause weird behavior in applications)....  I
personally think the stack trace is likely to be the best way to test
where the problem is.

Best Wishes,
Chris Travers

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-02-07 02:11:01
Subject: Re: Confusion over Python drivers
Previous:From: Josh BerkusDate: 2010-02-07 00:51:18
Subject: Re: Confusion over Python drivers

pgsql-bugs by date

Next:From: Robert HaasDate: 2010-02-07 04:20:07
Subject: Re: Possible stability issue: permanent hang on dropdb
Previous:From: Josh BerkusDate: 2010-02-07 00:47:30
Subject: Re: Possible stability issue: permanent hang on dropdb

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