Re: Parallel vacuum: I/O timings in the log leave out the parallel workers

From: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Subject: Re: Parallel vacuum: I/O timings in the log leave out the parallel workers
Date: 2026-09-28 21:48:27
Message-ID: CAN12+YLY63_ENAH4aNc03_WNHiL1cVGkoXH_bfBBu6z-TpHRYg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Bharath,

This looks good to me, and I wonder if we should do the same
for ANALYZE. It does the same exact thing. Although we don't
have parallel analyze now, if we ever get that we will need to
fix it there also, so let's just do it now.

--
Sami Imseih
Amazon Web Services (AWS)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2026-09-28 22:06:23 Costing for parallel scans with few/single row produced in the outer side
Previous Message Sami Imseih 2026-09-28 21:33:58 Re: parallel autovacuum: Propagate track_cost_delay_timing to parallel workers