On Sat, Feb 6, 2010 at 9:09 PM, Chris Travers <chris(at)metatrontech(dot)com> wrote:
> 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.
I suspect this is the same problem as bug #4897, and probably also the
same problem as this:
and maybe also this and this:
Unfortunately, it seems that no one has been able to get a stack trace yet.
The Enterprise Postgres Company
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2010-08-20 02:43:54|
|Subject: small smgrcreate cleanup patch|
|Previous:||From: KaiGai Kohei||Date: 2010-08-20 01:16:29|
|Subject: security hook on authorization|
pgsql-bugs by date
|Next:||From: Robert Haas||Date: 2010-08-20 01:46:10|
|Subject: Re: Automated analyze process fails with custom function,
which works perfect as regular user (8.4.2).|
|Previous:||From: Tatsuo Ishii||Date: 2010-08-19 23:29:57|
|Subject: Re: COPY FROM/TO losing a single byte of a multibyte UTF-8