News for hackers. Stuff that matters.
Re:PostgreSQL 11 Released by grouseway on Thursday October 18, 2018 @12:51PM (#18249922)
I'm a fairly casual PG user but I have these issues:

Lack of case and accent insensitive collations is inexcusable at this point. Is there anyone that enjoys sprinkling every bit of SQL with upper() comparisons?

Non materialized CTEs. I like materialized CTEs sometimes and wish MSSQL had them as an option but I also need it to work the other way.

Native point-in-time recovery out of the box. This looks like it might be possible but the process doesn't fill me with a lot of confidence.

Better connection scaling.

Ability to load custom TS dictionaries in user space (for hosted postgres on google/aws/etc..)

Re:PostgreSQL 11 Released by nathan_long on Thursday October 18, 2018 @02:12PM (#18250669)
> Is there anyone that enjoys sprinkling every bit of SQL with upper() comparisons?

Does using a citext column not solve this?

Re:PostgreSQL 11 Released by Tostino on Thursday October 18, 2018 @01:20PM (#18250207)
Agree on PITR being something that seems less approachable than it really is.

Use a tool like pgbackrest, and everything just works really well.