| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Thinking about EXPLAIN ALTER TABLE |
| Date: | 2018-12-10 16:45:49 |
| Message-ID: | CANP8+j+5ZOs=RzarxbhOzEPSuxzJvz9TicfJLkEkhBF4A-isuQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 10 Dec 2018 at 16:32, 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.
>
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/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-12-10 16:52:50 | Re: Thinking about EXPLAIN ALTER TABLE |
| Previous Message | s.cherkashin | 2018-12-10 16:38:39 | Re: Psql patch to show access methods info |