From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nagaraj Raj <nagaraj.sf@yahoo.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Issue with Running VACUUM on Database with Large Tables
Date: Mon, 25 Dec 2023 09:53:25 -0500
Message-ID: <1843284.1703516005@sss.pgh.pa.us> (raw)
In-Reply-To: <1237927313.5086260.1703506240368@mail.yahoo.com>
References: <1237927313.5086260.1703506240368.ref@mail.yahoo.com>
<1237927313.5086260.1703506240368@mail.yahoo.com>
Nagaraj Raj <nagaraj.sf@yahoo.com> writes:
> 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.
I can't replicate that. I get either
ERROR: relation "foo" does not exist
if you specifically name a nonexistent table, or
WARNING: skipping vacuum of "foo" --- relation no longer exists
if the table existed at the start but doesn't exist by the time
vacuum gets to it. There may be some code path that results in
the error you cite, but you'll need to provide more detail about
how to duplicate it.
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, nagaraj.sf@yahoo.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Issue with Running VACUUM on Database with Large Tables
In-Reply-To: <1843284.1703516005@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