Re: Handle concurrent drop when doing whole database vacuum

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, cca5507 <cca5507(at)qq(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>
Subject: Re: Handle concurrent drop when doing whole database vacuum
Date: 2026-08-03 21:10:01
Message-ID: anEDqYA_A030nAiH@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 09, 2026 at 01:56:02PM -0500, Nathan Bossart wrote:
> Cool, I'll address everyone's feedback and get this committed in the next
> few days.

Committed.

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-08-03 21:51:56 Re: Add pg_stat_kind_info system view
Previous Message Tomas Vondra 2026-08-03 20:36:17 Re: WAL compression setting after PostgreSQL LZ4 default change