From: Nagaraj Raj <nagaraj.sf@yahoo.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Issue with Running VACUUM on Database with Large Tables
Date: Mon, 25 Dec 2023 12:10:40 +0000 (UTC)
Message-ID: <1237927313.5086260.1703506240368@mail.yahoo.com> (raw)
References: <1237927313.5086260.1703506240368.ref@mail.yahoo.com>
Hello,
While executing a vacuum analyze on our database containing large tables (approximately 200k), I encountered an issue. If a table gets dropped during the vacuum process, the vacuum job fails at that point with an error message stating "OID relation is not found" and exits. This behavior seems to interrupt the entire process without providing a warning or handling the error gracefully.
Considering the possibility of dynamic objects within our database design, this abrupt termination makes it challenging to complete the vacuum process successfully. This issue has persisted across multiple versions, including the current version we're using (14.8).
Is this behavior expected or could it possibly be a bug? It would be beneficial to have a mechanism in place to handle such instances, perhaps by providing a notice or warning when encountering dropped tables, allowing the process to skip those tables and continue with the rest of the vacuum analyze.
Your support in resolving this matter is greatly appreciated.
Thanks,
Rj
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-bugs@postgresql.org
Cc: nagaraj.sf@yahoo.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Issue with Running VACUUM on Database with Large Tables
In-Reply-To: <1237927313.5086260.1703506240368@mail.yahoo.com>
* 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