Re: Report relation extension blockers within parallel lock groups

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Kirill Reshke <reshkekirill(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: Report relation extension blockers within parallel lock groups
Date: 2026-10-03 04:47:03
Message-ID: CAGRkXqTCURg-whHt-QVJ5+T7eiP=V-JFWwCrPJYEEF+3DfTtfQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Bertrand,

I reviewed and tested v1. The code change looks good to me.

> The description in the documentation is getting quite dense. This could
be
> a good opportunity to restructure it for readability.

The attached 0002 goes on top of v1.

It moves the prepared transaction sentence up and
gives parallel query its own paragraph.

Thanks,
Shihao

Attachment Content-Type Size
nocfbot-0002-Restructure-pg_blocking_pids-documentation.patch application/octet-stream 3.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2026-10-03 05:23:07 Re: [Patch]The Case For WAL-Logging pg_upgrade
Previous Message shihao zhong 2026-10-03 04:33:52 Re: [PATCH] Fix pg_dump emitting OVERRIDING SYSTEM VALUE for tables with dropped identity columns