![LIMIT vs Performance](https://img.transistor.fm/XoJKBsIida2PbzEhDlUv56LV_igZ6S4xTONrCcJ6P7A/rs:fill:800:800:1/q:60/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9zaG93/LzMyMTQ3LzE3MTA3/OTEzODMtYXJ0d29y/ay5qcGc.webp)
LIMIT vs Performance
Nikolay and Michael discuss LIMIT in Postgres — what it does, how it can help with performance, and an interesting example where adding it can actually hurt performance(!)
Here are some links to things they mentioned:
Here are some links to things they mentioned:
- LIMIT considered harmful in PostgreSQL (Twitter thread by Christophe Pettus) https://twitter.com/Xof/status/1413542818673577987
- LIMIT and OFFSET (docs) https://www.postgresql.org/docs/current/queries-limit.html
- No OFFSET (by Markus Winand) https://use-the-index-luke.com/no-offset
- LIMIT clause (docs) https://www.postgresql.org/docs/current/sql-select.html#SQL-LIMIT
~~~
What did you like or not like? What should we discuss next time? Let us know via a YouTube comment, on social media, or by commenting on our Google doc!
What did you like or not like? What should we discuss next time? Let us know via a YouTube comment, on social media, or by commenting on our Google doc!
~~~
Postgres FM is brought to you by:
- Nikolay Samokhvalov, founder of Postgres.ai
- Michael Christofides, founder of pgMustard
With special thanks to:
- Jessie Draws for the amazing artwork