Re: Thinking about EXPLAIN ALTER TABLE - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Thinking about EXPLAIN ALTER TABLE
Date
Msg-id CA+TgmoaXuAohxv7T7kKT57eMP4au=uBm5mf_nS7-QyxaoimRmw@mail.gmail.com
Whole thread Raw
In response to Re: Thinking about EXPLAIN ALTER TABLE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Thinking about EXPLAIN ALTER TABLE  (Michael Paquier <michael@paquier.xyz>)
Re: Thinking about EXPLAIN ALTER TABLE  (David Fetter <david@fetter.org>)
List pgsql-hackers
On Tue, Dec 11, 2018 at 1:32 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndquadrant.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


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Pluggable Storage - Andres's take
Next
From: Michael Paquier
Date:
Subject: Re: Should new partitions inherit their tablespace from their parent?