Sequential scan on Journal


(Shubham Agarwal) #1

Hello we are using postgres for DB, we saw lots of queries on journal table taking time doing sequential scan .
Query is : select “ordering”, “deleted”, “persistence_id”, “sequence_number”, “message”, “tags” from “journal” where (“tags” like ‘%%’) and (“ordering” >= ‘0’) order by “ordering” limit ‘9223372036854775807’ ---------------------- ANY idea why we have a query which does not scale.