From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com>, Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: DDL Damage Assessment |
Date: | 2014-10-03 03:07:36 |
Message-ID: | 542E12F8.1030800@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/2/14, 2:43 PM, Josh Berkus wrote:
>> >Questions:
>> >
>> > 1. Do you agree that a systematic way to report what a DDL command (or
>> > script, or transaction) is going to do on your production database
>> > is a feature we should provide to our growing user base?
> Yes.
+1
>> > 2. What do you think such a feature should look like?
> As with others, I think EXPLAIN is a good way to do this without adding
> a keyword. So you'd do:
>
> EXPLAIN
> ALTER TABLE ....
I'm thinking it would be better to have something you could set at a session level, so you don't have to stick EXPLAIN in front of all your DDL.
As for the dry-run idea, I don't think that's really necessary. I've never seen anyone serious that doesn't have a development environment, which is where you would simply deploy the real DDL using "verbose" mode and see what the underlying commands actually do.
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2014-10-03 03:16:07 | Re: proposal: doc: simplify examples of dynamic SQL |
Previous Message | Fabrízio de Royes Mello | 2014-10-03 02:38:58 | Re: Patch to add support of "IF NOT EXISTS" to others "CREATE" statements |