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

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Jeyaprakash Rajamani <jeyaprakash(dot)rajamani(at)chainsys(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Performance Degradation (Table becomes bloat) During Repeated Bulk UPDATE Operations
Date: 2026-06-18 17:24:38
Message-ID: CALj2ACUNT_NTjH7PbbRNHStvKOWiWu2=QE1Dh0-2T4A8uVDUEg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2026-06-18 17:37:06 Re: GUC parameter ACLs and physical walsender
Previous Message Jeyaprakash Rajamani 2026-06-18 17:15:48 Re: Performance Degradation (Table becomes bloat) During Repeated Bulk UPDATE Operations