Re: PGSQL ERROR: FATAL: terminating connection due to administrator command

From: Jorge Godoy <jgodoy(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Cc: "pobox(at)verysmall(dot)org" <pobox(at)verysmall(dot)org>
Subject: Re: PGSQL ERROR: FATAL: terminating connection due to administrator command
Date: 2008-02-04 11:01:08
Message-ID: 200802040901.08792.jgodoy@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Em Monday 04 February 2008 08:42:16 pobox(at)verysmall(dot)org escreveu:
> I have a PostgreSQL 8.2.6 on FreeBSD 6.3 (but the described behavior
> appears during several earlier minor versions as well) - which powers a
> php based web application. What I experience is the message (below)
> which appears during the first 5-7 clicks after the database has been
> cleanly imported (dropped and imported) -
>
> PGSQL ERROR: FATAL: terminating connection due to administrator command
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
>
> The message does not appear on every click. It can appear on the 1st,
> then not on the 2nd, then on the 3rd and so on. After few more clicks
> everything goes well until the next import.
>
> I could not find anything meaningful in the logs...
>
> Has somebody else experienced anything similar?

Have you checked your code and seen what is really happening on these clicks?
I had some cases where looking for unexisting information or trying to
operate on unexisting data crashed the specific process of the backend that
was serving my application.

Enable query logging and see what is happening.

--
Jorge Godoy <jgodoy(at)gmail(dot)com>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nicolas KOWALSKI 2008-02-04 11:40:19 Re: problem with ORDER BY
Previous Message Guido Neitzer 2008-02-04 10:45:53 Reload only specific databases from pg_dumpall