Re: Which SET TYPE don't actually require a rewrite

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Which SET TYPE don't actually require a rewrite
Date: 2020-07-21 20:55:37
Message-ID: 20200721205537.GB25122@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 17, 2020 at 11:26:56AM -0400, Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > As Amit mentions it is also triggered by some store parameter changes. But
> > not all. So looking at it the other way, the part that the end user really
> > cares about it "which ALTER TABLE operations will rewrite the table and
> > which will not". Maybe what we need is a section specifically on this that
> > summarizes all the different ways that it can happen.
>
> No, what we need is EXPLAIN for DDL ;-). Trying to keep such
> documentation in sync with the actual code behavior would be impossible.
> (For one thing, some aspects can be affected by extension datatype
> behaviors.)

I know Tom put a wink on that, but I actually do feel that the only
clean way to do this is to give users a way to issue the query in a
non-executing way that will report if a rewrite is going to happen.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com

The usefulness of a cup is in its emptiness, Bruce Lee

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2020-07-21 21:52:21 Re: Using Valgrind to detect faulty buffer accesses (no pin or buffer content lock held)
Previous Message Peter Eisentraut 2020-07-21 20:38:45 Re: Improving psql slash usage help message