In PostgreSQL, it often happens that you have an index on a field, but that index isn’t used when executing a query. You might wonder why. The reason could be that you are fetching a large amount of data, such as 70% or more. In such cases, fetching 70% or more of the data via an index is less efficient than a sequential scan. That’s why PostgreSQL opts for a sequential scan instead of an index scan, as the sequential scan is more efficient in this scenario. Why is that? Fetching a row using an index is almost four times costlier than performing a sequential scan. However, an index is still efficient when fetching a smaller number of records. Since we are dealing with a large amount of data here, PostgreSQL determines that a sequential scan will be more efficient in this case. #Database #PostgreSQL #performance #optimization

@sandip_nocode Do you use external data base in bubble ? I'm going to use @supabase (postgresql) as database for my bubble app.