Re: BUG #17212: pg_amcheck fails on checking temporary relations
Peter Geoghegan <pg@bowt.ie>
From: Peter Geoghegan <pg@bowt.ie>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Robert Haas <robertmhaas@gmail.com>,
Pavel Borisov <pashkin.elfe@gmail.com>, Alexander Lakhin <exclusion@gmail.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-10-11T18:40:34Z
Lists: pgsql-bugs, pgsql-hackers
On Mon, Oct 11, 2021 at 11:26 AM Mark Dilger <mark.dilger@enterprisedb.com> wrote: > That's fine by me, but I was under the impression that people wanted the extraneous noise removed. A NOTICE message is supposed to be surfaced to clients (but not stored in the server log), pretty much by definition. It's not unreasonable to argue that I was mistaken to ever think that about this particular message. In fact, I suspect that I was. > Since pg_amcheck can know the command is going to draw a "you can't check that right now" type message, one might argue that it is drawing these notices for no particular benefit. But technically it *was* checked. That's how I think of it, at least. If a replica comes out of recovery, and we run pg_amcheck immediately afterwards, are we now "checking it for real"? I don't think that distinction is meaningful. > Somebody could quite reasonably complain about this on a hot standby with millions of unlogged relations. Actual ERROR messages might get lost in all the noise. That's a good point. -- Peter Geoghegan
Commits
-
Remove unstable pg_amcheck tests.
- cd3f429d9565 15.0 landed
- 5863115e4cb1 14.1 landed
-
pg_amcheck: avoid unhelpful verification attempts.
- d2bf06db3779 15.0 landed
- dd58194cf563 14.1 landed
-
amcheck: Skip unlogged relations in Hot Standby.
- 292698f158dd 15.0 landed
- e7712155ea08 14.1 landed
-
amcheck: Skip unlogged relations during recovery.
- 6754fe65a4c6 13.0 cited