Re: Thinking about EXPLAIN ALTER TABLE

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Thinking about EXPLAIN ALTER TABLE
Date: 2018-12-11 02:25:12
Message-ID: CA+TgmoaXuAohxv7T7kKT57eMP4au=uBm5mf_nS7-QyxaoimRmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 11, 2018 at 1:32 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > I suggest ALTER TABLE should respond to a parameter setting of ddl_dry_run
> > = on, so the whole world doesn't need to rewrite its syntax to support the
> > new option.
>
> We were just busy shooting down a different suggestion of
> behavior-changing GUCs. A GUC that turns all ALTERs into no-ops
> sure seems like a foot-gun to me.

Yeah, I like EXPLAIN better.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-12-11 02:43:16 Re: Should new partitions inherit their tablespace from their parent?
Previous Message Andres Freund 2018-12-11 02:13:40 Re: Pluggable Storage - Andres's take