From: Justin Pryzby <pryzby@telsasoft.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [v15] ALTER TABLE ... SET ACCESS METHOD
Date: Wed, 5 May 2021 23:40:45 -0500
Message-ID: <20210506044045.GE27406@telsasoft.com> (raw)
In-Reply-To: <d66e14df5acd34ccb3ce83d8c052f8df44c78184.camel@j-davis.com>
References: <d66e14df5acd34ccb3ce83d8c052f8df44c78184.camel@j-davis.com>
On Wed, May 05, 2021 at 08:45:50PM -0700, Jeff Davis wrote:
> The attached patch implements ALTER TABLE ... SET ACCESS METHOD.
>
> For simplicity, I used the normal alter table path, ATRewriteTable(),
> which does not follow the stricter isolation semantics that VACUUM FULL
> follows. If someone thinks that's unacceptable, please let me know.
Why doees your patch say v15?
It's nearly the same as my pre-existing patch, so should merge them.
https://commitfest.postgresql.org/33/3020/
--
Justin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: pryzby@telsasoft.com, pgsql@j-davis.com
Subject: Re: [v15] ALTER TABLE ... SET ACCESS METHOD
In-Reply-To: <20210506044045.GE27406@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox