From: Tom Lane <tgl@sss.pgh.pa.us>
To: Leandro Bugalho <leandrohb@gmail.com>
cc: pgsql-admin@lists.postgresql.org, Zaid Shabbir <zaidshabbir@gmail.com>
Subject: Re: Error when execute insert/update
In-reply-to: 
 <CAExYQ-owooDMu6uWjWdYcAt2LAvKSEt8S3vtuhNL017hFDEOCA@mail.gmail.com>
References: 
 <CAExYQ-pMgOt1V-oDjoa+bv=xfEM2PfnaHkPTiwr9oSv-_w1ONQ@mail.gmail.com>
 <CABCJe_VDtmVDn7nYzRHqF3TKkajfQbj2cSPcBooPgKQ+Bkv8KA@mail.gmail.com>
 <CAExYQ-owooDMu6uWjWdYcAt2LAvKSEt8S3vtuhNL017hFDEOCA@mail.gmail.com>
Comments: In-reply-to Leandro Bugalho <leandrohb@gmail.com>
	message dated "Sun, 11 Sep 2022 08:35:28 -0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <816925.1662909249.1@sss.pgh.pa.us>
Date: Sun, 11 Sep 2022 11:14:09 -0400
Message-ID: <816926.1662909249@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/816926.1662909249%40sss.pgh.pa.us>
Precedence: bulk

Leandro Bugalho <leandrohb@gmail.com> writes:
> This upgrade is in our follow up. But unfortunately this issue
> occurred previously our upgrade.  Now we need to fix this. ANy
> suggestions ?

There is no magic bullet that will avoid the need for the cleanup
VACUUM, if that's what you mean.  What you should be thinking
about is how to prevent a recurrence of the situation.  In ordinary
circumstances autovacuum ought to have kept you out of trouble ...
have you disabled that, or changed settings to render it
insufficiently aggressive?

			regards, tom lane