Re: Allow single table VACUUM in transaction block

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, 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-17 20:06:43
Message-ID: CA+Tgmoa8gKKi_xbOmgVAgANhvMGRMTT2wJKrXsB+yZEFtv=DaA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 16, 2022 at 5:14 PM Greg Stark <stark(at)mit(dot)edu> wrote:
> However I'm not a fan of commands that sometimes do one thing and
> sometimes magically do something very different. I don't like the idea
> that the same vacuum command would sometimes run in-process and
> sometimes do this out of process request. And the rules for when it
> does which are fairly complex to explain -- it runs in process unless
> you're in a transaction when it runs out of process unless it's a
> temporary table ...

100% agree.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-11-17 20:13:04 Re: ubsan fails on 32bit builds
Previous Message Robert Haas 2022-11-17 20:04:57 Re: redundant check of msg in does_not_exist_skipping