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
Date: Sun, 11 Sep 2022 11:14:09 -0400
Message-ID: <816926.1662909249@sss.pgh.pa.us> (raw)
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>
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
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, leandrohb@gmail.com, zaidshabbir@gmail.com
Subject: Re: Error when execute insert/update
In-Reply-To: <816926.1662909249@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