Postgres Pro
Downloads
Home   >   mailing lists

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

From Simon Riggs
Subject Re: Thinking about EXPLAIN ALTER TABLE
Date
Msg-id CANP8+j+5ZOs=RzarxbhOzEPSuxzJvz9TicfJLkEkhBF4A-isuQ@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  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view
On Mon, 10 Dec 2018 at 16:32, 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.

How would you test a script? Manually edit each one with the new option? Manual editing is more of a foot gun.

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: s.cherkashin@postgrespro.ru
Date:
Subject: Re: Psql patch to show access methods info
Next
From: Tom Lane
Date:
Subject: Re: Thinking about EXPLAIN ALTER TABLE