You can avoid this issue by adding an unneeded ORDER BY
clause to the query.
SELECT * FROM object_values WHERE (objectID = 53708) ORDER BY timestamp, objectID DESC limit 1;
More Related Contents:
- PostgreSQL LIKE query performance variations
- Postgres query optimization (forcing an index scan)
- Optimize Postgres query on timestamp range
- Insert, on duplicate update in PostgreSQL?
- invalid byte sequence for encoding “UTF8”
- Postgresql: Conditionally unique constraint
- How to make “case-insensitive” query in Postgresql?
- Rownum in postgresql
- dynamic sql query in postgres
- Cannot create a database table named ‘user’ in PostgreSQL
- Is there a timeout for idle PostgreSQL connections?
- How to make connection to Postgres via Node.js
- Postgresql Truncation speed
- How can I speed up a MySQL query with a large offset in the LIMIT clause?
- Buffers (Circle) in PostGIS
- How to get function parameter lists (so I can drop a function)
- Unable to connect PostgreSQL to remote database using pgAdmin
- How to convert a postgres database to sqlite
- How does PostgreSQL perform ORDER BY with a b-tree index on the field?
- Error when setting n_distinct using a plpgsql variable
- Docker wait for postgresql to be running
- Function to loop through and select data from multiple tables
- Switch role after connecting to database
- SQL Sub queries in check constraint
- When do Postgres column or table names need quotes and when don’t they?
- How can I get a list of all functions stored in the database of a particular schema in PostgreSQL?
- Composite PRIMARY KEY enforces NOT NULL constraints on involved columns
- PostgreSQL how to concat interval value ‘2 days’
- Displaying image in Ireports using PostgreSql
- Spring Docker container cannot access Postgres Docker container