From: Tom Lane <tgl@sss.pgh.pa.us>
To: liam saffioti <liam.saffiotti@gmail.com>
Cc: Avinash Vallarapu <avinash.vallarapu@gmail.com>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: autoovacuum launcher process
Date: Mon, 13 Sep 2021 09:46:14 -0400
Message-ID: <358010.1631540774@sss.pgh.pa.us> (raw)
In-Reply-To: <CAGHjuaZ=w39Od5b4DcwR8hMC+GwzMXaP8Wsk8FxsigPJjXB5xQ@mail.gmail.com>
References: <CAGHjuabpW8M=h=1FfCR9LgAFGASMKKnz+kE7d5oqNMvSOsOcxA@mail.gmail.com>
<214794.1631455943@sss.pgh.pa.us>
<CAGHjuaapbvKjurPUNRzk8mwD+pocRhFyj=n_YSVQmBMMsTsF-A@mail.gmail.com>
<CAN0Tujckx4ZVxZUhr3EkrVOBDny+8-RTAqhXUL-GWbNT0Sm3Ow@mail.gmail.com>
<CAGHjuaZLHwK0+8ugyEC40t43Tu799OjcFnLzk00kv29KPhbsxg@mail.gmail.com>
<CAN0TujdA1r8mfoxAAw=e9Lf9axg-C7Lt2WRvSWEV0Kuw8wSg+A@mail.gmail.com>
<CAGHjuaYt+z5b6tWAZDxMXwesF3wn8VxhonQ_ky3NYDA1_BCwaw@mail.gmail.com>
<CAGHjuaZ=w39Od5b4DcwR8hMC+GwzMXaP8Wsk8FxsigPJjXB5xQ@mail.gmail.com>
liam saffioti <liam.saffiotti@gmail.com> writes:
> Do you think timescaledb is causing this problem?
Seems possible.
> 2021-09-10 01:00:32.691 156668 FATAL: cannot read pg_class without
> having selected a database
> 2021-09-10 01:00:33.356 110257 LOG: autovacuum launcher process (PID
> 156668) exited with exit code 1
This is pretty clear evidence that some code running inside the
autovacuum launcher process tried to read a non-shared catalog, which it
cannot do because the launcher isn't connected to any specific database
within the cluster. It is highly unlikely that anything in core Postgres
is doing that; we'd have noticed. So I conclude that some extension code
is carelessly trying to do catalog accesses without checking to see if
it's running in a background process that doesn't support that.
Of the extensions you listed, timescaledb is perhaps the most likely to
contain such a bug; but I don't know much about hypopg, pg_partman,
pg_stat_kcache, or powa, so I can't completely rule those out. It would
have to be an extension that sometimes acts of its own accord without
being called by a SQL command, so the list of suspects isn't all that
long.
Anyway, your first step should be to make sure you have up-to-date
versions of all those extensions. If you do, then try filing a bug
with timescaledb.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, liam.saffiotti@gmail.com, avinash.vallarapu@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: autoovacuum launcher process
In-Reply-To: <358010.1631540774@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox