Re: Allow single table VACUUM in transaction block

From: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Allow single table VACUUM in transaction block
Date: 2022-11-14 19:52:04
Message-ID: CANbhV-EW7wBTqzn30N1XMGsWfrYXhb0eG9soP7JcX-P30ZxVcA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 8 Nov 2022 at 03:10, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> wrote:
>
> On Mon, 7 Nov 2022 at 08:20, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> wrote:
>
> > Temp tables are actually easier, since we don't need any of the
> > concurrency features we get with lazy vacuum.

> Thoughts?

New patch, which does this, when in a xact block

1. For temp tables, only VACUUM FULL is allowed
2. For persistent tables, an AV task is created to perform the vacuum,
which eventually performs a vacuum

The patch works, but there are various aspects of the design that need
input. Thoughts?

--
Simon Riggs http://www.EnterpriseDB.com/

Attachment Content-Type Size
single_table_vacuum_in_xact.v3.patch application/octet-stream 16.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Christensen 2022-11-14 19:59:04 Re: [PATCH] Teach pg_waldump to extract FPIs from the WAL
Previous Message Robert Haas 2022-11-14 19:32:16 Re: Add sub-transaction overflow status in pg_stat_activity