Postgres 11 – A First Look • Hacker News Board

Re: Postgres 11 – A First Look

#191

Post by eip » Mon, Sep 24, 2018, 8:13 PM UTC

craigkerstiens wrote: post #22

jorams wrote: post #3

> Now you can quit Postgres by simply typing quit or exit. Previously you had to use Ctrl + D or \q While this is good to help out beginners a bit, people should really learn Ctrl + D. It works practically everywhere and saves tons of time guessing/remembering and even typing the correct incantation for the program you want to exit.

Original author here. Yes, it's great to learn Ctrl + D. But losing out on beginners that aren't familiar in favor of things that are naturally intuitive is a great way to make those who are new to programming and especially databases feel like they're dumb or not capable of it. I still recall the first time I was in vi and I couldn't figure out how to get out of the damn thing, and don't get me started on arrow keys…

> Ctrl+D

> things that are naturally intuitive

Pick one

Re: Postgres 11 – A First Look

#192

Post by mb4nck » Sat, Oct 06, 2018, 12:04 PM UTC

booleanbetrayal wrote: post #146

nathan_f77 wrote: post #112

> Fear column addition no more This section was really surprising to read! I use the strong_migrations [1] gem to catch "NOT NULL column with a default value", because it's such a common mistake. I guess I had assumed that this was just something we had to accept, based on decades of architecture decisions, and the way that Postgres was written. It never occurred to me that it was actually possible to change the defa…

This feature has me way more excited than I probably should be. Been splitting up relatively simple schema migrations into multiple steps for years now, and definitely welcoming this change.

Notably, that feature got written by somebody from Salesforce (I assume on their work time, but not sure), and finished up by a Postgres major contributor. It might be the first major contribution from Salesforce outside of all the stuff Tom Lane did when he was working there.

Re: Postgres 11 – A First Look

#193

Post by petergeoghegan » Sat, Oct 06, 2018, 9:48 PM UTC

mb4nck wrote: post #192

booleanbetrayal wrote: post #146

Earlier quoted context omitted.

This feature has me way more excited than I probably should be. Been splitting up relatively simple schema migrations into multiple steps for years now, and definitely welcoming this change.

Notably, that feature got written by somebody from Salesforce (I assume on their work time, but not sure), and finished up by a Postgres major contributor. It might be the first major contribution from Salesforce outside of all the stuff Tom Lane did when he was working there.

Not so. I worked on UPSERT for several years as a Salesforce employee, as well as quite a number of other things. I worked for Heroku, a Salesforce business unit, from 2013-2017.