7 ms·
PostgreSQL 11 and Just in Time Compilation of Queries
- minxomat 8y agoHPE did an excellent technical, no marketing BS writeup on PG11[0]. I highly recommend everyone interested in the new features read this. [0] https://h50146.www5.hpe.com/products/software/oe/linux/mainstream/support/lcc/pdf/PostgreSQL_11_New_Features_beta1_en_20180525-1.pdf https://h50146.www5.hpe.com/products/software/oe/linux/mains...
- thisgoodlife 8y agoCool! Is there a similar doc for pg10? I'm still using 9.5. Thanks!
- amitlan 8y agoThere is: PostgreSQL 10 New Features With Examples https://h50146.www5.hpe.com/products/software/oe/linux/mainstream/support/lcc/pdf/PostgreSQL_10_New_Features_en_20170522-1.pdf https://h50146.www5.hpe.com/products/software/oe/linux/mains...
- citilife 8y agoI'm curious if we will see similar improvements for full-text search. If PostgreSQL continues to improve at this rate, there will be little reason to use many of alternatives... Personally, I already view PostgreSQL comparable (for many use cases) to paid options[1]. Interesting, for queries such as: EXPLAIN ANALYZE SELECT * FROM (SELECT * FROM sort1 ORDER BY 1) AS a LIMIT 5 ; You'll see an order of magnitude speed improvement (page 47 of [2]). [1] https://austingwalters.com/fast-full-text-search-in-postgresql/ https://austingwalters.com/fast-full-text-search-in-postgres... [2] https://h50146.www5.hpe.com/products/software/oe/linux/mainstream/support/lcc/pdf/PostgreSQL_11_New_Features_beta1_en_20180525-1.pdf https://h50146.www5.hpe.com/products/software/oe/linux/mains...
- anarazel 8y agoI doubt it unfortunately - the FTS operators are too heavyweight to be inlined (or benefit from inlining), so JIT isn't likely to help a ton. Parallelism can help however, depending on what your bottleneck is (if the query produces a bitmap indexscan the heap access part can be parallelized).
- SigmundA 8y agoSeriously if PG gets better text search to put it on par with Lucene (Rum indexes, BM25 and TF*IDF) I don't see much reason to use anything else either.
- sandGorgon 8y agoexactly this. I wish they would update the relevance algorithms to use TFIDF and BM25. We've been praying for this for a long time.. and not really sure why they havent been implemented.
- fgonzag 8y agoMy guess would be because no developer with the skillet necessary has either been interested or been paid to do it. It is an open source project at the end of the day, which means the features that get added are those that are wanted by either the developers or the sponsors, not the the general user base
- qaq 8y agoActually this might be a good idea for kickstarter if anyone with relevant experience is around :) I bet it would not be a problem to raise 200-300K for this
- sandGorgon 8y agoi would definitely contribute. BTW - elastic.co is just going for an IPO. There's a lot of money in search!
- munk-a 8y agoIt looks like (reading through the release notes and some not very recent mailing list threads) that CTE optimization fences will not be removed in PostgreSQL 11. This makes me very sad.
- jeltz 8y agoThere is a work in progress patch (https://commitfest.postgresql.org/19/1734/ https://commitfest.postgresql.org/19/1734/) which you can help out with by reviewing and testing it.
- paulddraper 8y agoPostgreSQL for all its great points has the worst hinting strategy in the world. There's no hinting because the planner is so smart, and yet there is mandatory hinting on a legitimately useful language construct that in some cases is the only way to do something (e.g. recursive queries). Just a very weird philosophy.
- jarym 8y agoVery exciting stuff happening in the PG world. One of the items I'm watching is support for foreign keys in arrays - https://commitfest.postgresql.org/17/1252/ https://commitfest.postgresql.org/17/1252/ Author is currently stuck and I hope someone with the right knowledge can help him out so he can continue the work.