| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: A Modest Upgrade Proposal |
| Date: | 2016-07-18 22:33:30 |
| Message-ID: | 578D593A.3000002@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/18/2016 03:17 PM, Jim Nasby wrote:
> On 7/17/16 2:22 PM, Petr Jelinek wrote:
> I do agree that DDL "feels better" (which I think is what JD was
> alluding too).
Yes and no. It reads better and is more clear to those who are not
developers or have a developer background which is, many in the database
field. It is also easier to type. I type 120 a minute on a roll, that is
until I have to do this ('[ ..... Simple wording base command structure
is much more efficient.
ALTER TABLE FOO ENABLE REPLICATION ON SLAVE 0;
vs
select enable_replication_for_table('['foo']',0);
Guess which one was typed without a single error and more quickly.
Sincerely,
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-07-19 00:33:20 | Re: One process per session lack of sharing |
| Previous Message | Tom Lane | 2016-07-18 22:30:17 | Re: application_name in process name? |