Обсуждение: Re: Getting FATAL: terminating connection due to administrator command

--------Tom Lane <tgl@sss.pgh.pa.us> wrote--------
Subject: Re: [GENERAL] Getting FATAL: terminating connection due to administrator command 
Date: 16.09.2010 17:37

>Peter Hopfgartner <peter.hopfgartner@r3-gis.com> writes:
>> Now we had the error, but systemtap did not report any SIGTERM. Is it
>> possible to have this error without a SIGTERM being involved?
>
>Hmph.  I would have said not, but ...
>
>What PG version is this exactly?
>
>            regards, tom lane
>

It says:

"PostgreSQL 8.4.4 on x86_64-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48), 64-bit"

and should be identical to the current Red Hat implementation of postgresql84-server as in RHEL 5.5

Peter

Peter Hopfgartner <peter.hopfgartner@r3-gis.com> writes:
> --------Tom Lane <tgl@sss.pgh.pa.us> wrote--------
>> Peter Hopfgartner <peter.hopfgartner@r3-gis.com> writes:
>>> Now we had the error, but systemtap did not report any SIGTERM. Is it
>>> possible to have this error without a SIGTERM being involved?
>>
>> Hmph.  I would have said not, but ...
>>
>> What PG version is this exactly?

> "PostgreSQL 8.4.4 on x86_64-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48), 64-bit"

Well, I just took another careful look at the 8.4.x source code.  The
only occurrence of that error string is in ProcessInterrupts() when it
sees ProcDiePending set, and so far as I can see ProcDiePending is only
set by the die() signal handler, and in postmaster child processes die()
is only used as a SIGTERM handler.  So it's pretty hard to come to the
conclusion that it could be anything else.

I don't know systemtap well at all, so I can't suggest any reason why
your script might be missing SIGTERM events, but it seems that it must be.
Perhaps you can find a systemtap expert who can comment on that.

            regards, tom lane