Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I wished they would implement more from SQL:2011. I have a lot of applications that would benefit from system versioned tables.

This is a good sum up of useful modern SQL features: https://www.slideshare.net/MarkusWinand/modern-sql



I was expecting that presentation to be stuff you were missing, but the presentation is saying that essentially every feature they describe is implemented in PostgreSQL. Of the SQL:2011 ones, only one wasn't (temporal tables), and even the SQL:2016 features had partial support (with the summary slide at the end of other features they didn't do in detail having stuff that looks familiar in a PostgreSQL context). Do you have a reference of features not in PostgreSQL you are hoping to use?


I really would like to use Temporal Tables (slides 137 and following) to say like 'give me the record of last week'.

I can of course do that already manually, but it is tedious and I hope it will be faster if implemented directly.


Besides temporal tables, I want temporal materialized views. I needed such a thing so much so that I implemented such a thing in PlPgSQL: https://github.com/twosigma/postgresql-contrib/blob/master/p...

This lets me materialize a view and then inspect deltas between refreshes, with history, and even update the materialized view from triggers and have those changes recorded in a history table automatically.



Thanks for the link!



Time travel existed for a long time, but eventually got culled in v8 (IIRC) because not enough people were using it to justify the code complexity.


Get involved in the mailing list and start discussion on these features and how they would help you.


I fear I cannot contribute a lot in my extremely limited time. Is there a 'getting started' guide somewhere?


Honestly you don't even have to submit a single patch to contribute.

Here is the developer's FAQ: https://wiki.postgresql.org/wiki/Developer_FAQ

I know the feeling of having extremely limited time, i'm in the same boat. But I use Postgres every day with my startup, and we lean very heavy on the database (not by volume of data, just by complexity of the problems). I've reviewed a few patches that I wanted to see get into Postgres, and contributed to discussions on the mailing list. That's about the extent I am able to do at the moment, but it's better than nothing. More reviewers are never a bad thing.


this slide deck is pure gold, just what i needed. thanks!


Glad I could help!

Here's the recording for that very presentation, by the way. https://www.youtube.com/watch?v=8wMybGTlf8I




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: