From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rainer Tammer <pgsql@spg.schulergroup.com>
cc: "David G. Johnston" <david.g.johnston@gmail.com>,
        PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: Postgres 9.2.13 on AIX 7.1
In-reply-to: <5e4f9356-26cc-bd75-4f82-92d26ce575f7@spg.schulergroup.com>
References: <77b4c413-b6ce-f07c-0d8b-a4ec8b5eec88@spg.schulergroup.com>
 <3821572.1628615273@sss.pgh.pa.us>
 <20217971-0a12-6a39-2b54-c13008afc3f0@spg.schulergroup.com>
 <CAKFQuwZV3TR_ou+DXadrYGik2W7vd-kfRwP0F7Q-Wdp_0vt7-g@mail.gmail.com>
 <fe2f0005-da96-1508-6139-d6ac3d99af59@spg.schulergroup.com>
 <582099.1629904402@sss.pgh.pa.us>
 <5e4f9356-26cc-bd75-4f82-92d26ce575f7@spg.schulergroup.com>
Comments: In-reply-to Rainer Tammer <pgsql@spg.schulergroup.com>
	message dated "Wed, 25 Aug 2021 18:04:17 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <585488.1629908370.1@sss.pgh.pa.us>
Date: Wed, 25 Aug 2021 12:19:30 -0400
Message-ID: <585489.1629908370@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/585489.1629908370%40sss.pgh.pa.us>
Precedence: bulk

Rainer Tammer <pgsql@spg.schulergroup.com> writes:
> It did run the server with auto vacuum disabled for ~ 24h - no server 
> shutdown.
> After re-enabling auto vacuum the server dies in less then 9 hours:

This is just speculation, but it fits the reported facts: somewhere
you've got something that tries to limit the resources consumed by
a background process, and when it decides the limit is exhausted
then it sends SIGINT.  Without autovacuum waking up every so often,
the time for PG-as-a-whole to hit the hypothetical limit would be
much longer.

> Would it be worth adding additional code before every signal to trace 
> the source ID and the target PID as well as the source/target process name?

I will be *mightily* astonished if the signal is coming from
within PG.  The more so since it appears to be happening while
the instance is entirely idle.

			regards, tom lane