Re: Performance Degradation (Table becomes bloat) During Repeated Bulk UPDATE Operations

Hi,

Vacuum verbose doesn't show anything in detail. It only shows 'vacuuming
table_name'.

*With Regards,*
*Jeyaprakash R*
*PostgreSQL DBA | AppSupport *

On Thu, 18 Jun 2026, 22:54 Bharath Rupireddy, <
bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:

> Hi,
>
> On Thu, Jun 18, 2026 at 10:16 AM Jeyaprakash Rajamani
> <jeyaprakash(dot)rajamani(at)chainsys(dot)com> wrote:
> >
> > But why doesn't VACUUM remove the dead tuples? We also checked at that
> time and confirmed there are no long running, active transactions or
> replication slots.
>
> You may need to look at the VACUUM verbose output - it would tell you
> exactly how many dead tuples/pages are present but not removable and
> what's the oldest-xmin (which vacuum uses to decide whether or not to
> remove the dead tples) etc.
>
> --
> Bharath Rupireddy
> Amazon Web Services: https://aws.amazon.com
>

--

----
Disclaimer:
This message may contain confidential and/or privileged
information.  If you are not the addressee or authorized to receive this
for the addressee, you must not use, copy, disclose, or take any action
based on this message or any information herein.  If you have received this
message in error, please advise the sender immediately by reply e-mail and
delete this message.  The opinion expressed in this mail is that of the
sender and do not necessarily reflect that of ChainSys. Thank you for your
co-operation.