Re: BUG #5442: Postgres crash when closing a "/console" mstsc session

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: sdelforge(at)free(dot)fr
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5442: Postgres crash when closing a "/console" mstsc session
Date: 2010-04-29 23:27:56
Message-ID: 4BDA15FC.3050800@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 29/04/2010 8:26 PM, sdelforge(at)free(dot)fr wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5442
> Logged by:
> Email address: sdelforge(at)free(dot)fr
> PostgreSQL version: 8.4.3
> Operating system: Windows 2003
> Description: Postgres crash when closing a "/console" mstsc session
> Details:
>
> Hello,
>
> I have nearly the same bug than "BUG #5305", but it occurs only with
> /console mode.
>
> Postgres is working as a windows service under the "postgres" user. We log
> on the Windows server by using mstsc and we have sometimes a crash of a
> prostgres process with "Exit code 128" which stop the postgres service.
> After analysing, we saw that the crash occurs only when the "\console"
> session stop (but not every time).
>
> We are able to reproduce this crash:
> 1- Open an mstsc Windows session with "\console" and user Administrator
> 2- Open a standard mstsc Windows session with antoher user
> 3- In this new session, execute a process which is doing some requests on
> the database and at the same time execute a database backup with pgAdmin
> 4- Close the "\console" session

Is there any chance you can follow these instructions:

http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows

and get a backtrace of the crash?

--
Craig Ringer

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Claudio 2010-04-30 03:51:16 BUG #5443: Undetected deadlock situation
Previous Message Andres Freund 2010-04-29 23:14:33 plpython memory leak uppon empty resultsets in all versions