Re: Handle concurrent drop when doing whole database vacuum

From: surya poondla <suryapoondla4(at)gmail(dot)com>
To: cca5507 <cca5507(at)qq(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Handle concurrent drop when doing whole database vacuum
Date: 2026-06-29 05:01:07
Message-ID: CAOVWO5pCNLbCsuhQHb+gCJMND5AsXv6SB3TMiwBH+q_1rmwOww@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi All,

The new patch (v6) with the Assertion check looks good to me.

Regards,
Surya Poondla

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Henson Choi 2026-06-29 05:05:39 Re: Add wait events for server logging destination writes
Previous Message cca5507 2026-06-29 04:58:51 Re: Handle concurrent drop when doing whole database vacuum