Postgres 11 – A First Look

&gt; Fear column addition no more<p>This section was really surprising to read! I use the strong_migrations [1] gem to catch &quot;NOT NULL column with a default value&quot;, because it&#x27;s such a common mistake.<p>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 default behavior of Postgres and fix the underlying issue.<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;ankane&#x2F;strong_migrations#adding-a-column-with-a-default-value" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ankane&#x2F;strong_migrations#adding-a-column-...</a>

&gt; Now you can quit Postgres by simply typing quit or exit. Previously you had to use Ctrl + D or \q<p>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&#x2F;remembering and even typing the correct incantation for the program you want to exit.

A million things like this are why PostgreSQL is the only relational database I consider for, well, pretty much anything. Their approach of “build it safe and then make it fast” has been paying off in spades for a couple of decades now. Thanks for everything you do, psql maintainers!

Thank you pg maintainers, you&#x27;ve made such a wonderful thing.

I have a serious problem with Postgres. Every year at FOSDEM, some of the most technically interesting talks are about Postgres, and the room is always far too small so I can&#x27;t get in.

One thing the OP didn’t mention is that the JIT is not enabled by default. They found that it has performance improvements for only long and complex queries yet. [1] But it can be enabled by a simple configuration command: jit = on.<p>[1]: <a href="https:&#x2F;&#x2F;www.phoronix.com&#x2F;scan.php?page=news_item&amp;px=PostgreSQL-JIT-No-11-Default" rel="nofollow">https:&#x2F;&#x2F;www.phoronix.com&#x2F;scan.php?page=news_item&amp;px=PostgreS...</a>

I’m already loving PG10’s native partitioning support. PG11 closes the loop on a few convenience features like being able to set foreign and primary keys at the master table level. With PG10 I can’t use ON CONFLICT clauses - looking forward to upgrading and sorting that out.

I&#x27;m excited for hash partitioning. Being able to partition on a uuid is going to be very useful.

I love Postgres, but the only thing I find myself wishing for was better Unicode support in the regex engine. I like to add strong database constraints, and sometimes lean on the regexp engine but I find it&#x27;s missing a lot of features available in other regexp engines. PCRE compatibility would be ideal, but even just support for the Unicode \p classes would be a big step up.

I love PG. heaps better than the alternatives, for many reasons. My main one, is native IPv6 object support.<p>I found the migration from 9.x to 10.x deeply painful, I think the one-time cost of the dump-restore cycle hurt me far more than I expected. I very much hope the transition to 11 can be done more expeditiously.

What are some reasons I might consider Postgres over MySQL when choosing a DB platform?

Great looking release. I’m really excited to see if the cstore extension can make good use of the parallelism improvements.