On Mon, Feb 1, 2010 at 11:28 AM, Cristian <cbittel@gmail.com> wrote:
>
> The following bug has been logged online:
>
> Bug reference: =A0 =A0 =A05305
> Logged by: =A0 =A0 =A0 =A0 =A0Cristian
> Email address: =A0 =A0 =A0cbittel@gmail.com
> PostgreSQL version: 8.3.9
> Operating system: =A0 Windows 2003 Server Standard x64
> Description: =A0 =A0 =A0 =A0Postgres service stops when closing Windows s=
ession
> Details:
>
> We connect to Windows server using the Terminal Services Clients (mstsc),
> and performs maintenance task with pgAdmin 3.
>
> PostgreSQL service crashes when the user close session on Windows, and the
> following error is recorded in the pg_log files:
>
>
>
> LOG: =A0server process (PID 5200) exited with exit code 128
>
> LOG: =A0terminating any other active server processes
>
> WARNING: =A0terminating connection because of crash of another server pro=
cess
>
> DETAIL: =A0The postmaster has commanded this server process to roll back =
the
> current transaction and exit, because another server process exited
> abnormally and possibly corrupted shared memory.
>
> HINT: =A0In a moment you should be able to reconnect to the database and
> repeat your command. ..
>
>
>
> The server has the following specs:
>
> Windows 2003 SP2 Standard 64-bit, 4GB, NOT joined to a domain.
>
> PostgreSQL 8.3.9
>
> pgAdmin 3
>
> We connect without the /console parameter.
>
>
> Any ideas?
So you're saying that if pgadmin is open when you close the terminal
services session, the SERVER crashes?
Did you somehow start the server in that same session, or is the
server running as a service?
...Robert
