Skip to main content
AI Assist is now on Stack Overflow. Start a chat to get instant answers from across the network. Sign up to save and share your chats.

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • ... but PostgreSQL doesn't have query hints. No. Really. ;-) Commented Feb 15, 2013 at 15:27
  • I have similar issue but with single query, postgres decides to do full table scan instead of index scan leading to killing database. And it does it only sometimes. The returned number of rows is set to 10, and it fails even when there is none to return. Whenever it picks index - extremely fast, picks to use table scan - rows scan over millions of records. I wonder if OFFSET 0 can help when this is not a subquery? Commented Dec 9, 2020 at 9:15