| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rainer Tammer <pgsql(at)spg(dot)schulergroup(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres 9.2.13 on AIX 7.1 |
| Date: | 2021-08-25 16:19:30 |
| Message-ID: | 585489.1629908370@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Rainer Tammer <pgsql(at)spg(dot)schulergroup(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-08-25 20:00:01 | BUG #17161: Assert failed on opening a relation that exists in two schemas via the LANGUAGE SQL function |
| Previous Message | Rainer Tammer | 2021-08-25 16:04:17 | Re: Postgres 9.2.13 on AIX 7.1 |