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
In-reply-to: <1237927313.5086260.1703506240368@mail.yahoo.com>
References: <1237927313.5086260.1703506240368.ref@mail.yahoo.com>
 <1237927313.5086260.1703506240368@mail.yahoo.com>
Comments: In-reply-to Nagaraj Raj <nagaraj.sf@yahoo.com>
	message dated "Mon, 25 Dec 2023 12:10:40 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1843283.1703516005.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Dec 2023 09:53:25 -0500
Message-ID: <1843284.1703516005@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1843284.1703516005%40sss.pgh.pa.us>
Precedence: bulk

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 dur=
ing the vacuum process, the vacuum job fails at that point with an error m=
essage 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