Request a Demo
Home   >   mailing lists

Re: Performance Degradation (Table becomes bloat) During Repeated Bulk UPDATE Operations - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Performance Degradation (Table becomes bloat) During Repeated Bulk UPDATE Operations
Date
Msg-id CALj2ACUNT_NTjH7PbbRNHStvKOWiWu2=QE1Dh0-2T4A8uVDUEg@mail.gmail.com
Whole thread
In response to Re: Performance Degradation (Table becomes bloat) During Repeated Bulk UPDATE Operations  (Jeyaprakash Rajamani <jeyaprakash.rajamani@chainsys.com>)
Responses Re: Performance Degradation (Table becomes bloat) During Repeated Bulk UPDATE Operations
List pgsql-hackers
Tree view 
Hi,

On Thu, Jun 18, 2026 at 10:16 AM Jeyaprakash Rajamani
<jeyaprakash.rajamani@chainsys.com> wrote:
>
> But why doesn't VACUUM remove the dead tuples? We also checked at that time and confirmed there are no long running,
activetransactions 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

pgsql-hackers by date:

Previous
From: Jeyaprakash Rajamani
Date:
Subject: Re: Performance Degradation (Table becomes bloat) During Repeated Bulk UPDATE Operations
Next
From: Jeff Davis
Date:
Subject: Re: GUC parameter ACLs and physical walsender