CODEWITHSUNDEEP
postgresql
Sujit
Sujit

Reputation: 2441

finding MAX(db_timestamp) query

I have BIG table with multiple indexes in postgres. It has indexes on db_timestamp, id, username.

I want to find the MAX timestamp for particular username. The problem is the simple query like 

SELECT MAX(db_timestamp) FROM Foo WHERE username = 'foo'

takes so much time because of the huge table size( we are talking 450GB table with over 30 GB index sizes).

Is their any way to optimize this query or tell postgres about what query plan to use?

Upvotes: 0

Views: 2280

Answers (2)

Frank Heikens
Frank Heikens

Reputation: 127086

Use create an index on username and db_timestamp with correct sort order:

CREATE INDEX idx_foo ON foo (username ASC, db_timestamp DESC);

Check EXPLAIN to see if things work as they should.

Upvotes: 2

araqnid
araqnid

Reputation: 133482

Postgresql can't use the index on (db_timestamp,id,username) to satisfy that query- the query term you're after has to be a prefix of the index, i.e. using the first column(s).

So an index on (username,db_timestamp) would serve that query very well, since it just has to scan the subtree (username,0)..(username,+inf) (and iirc Postresql should actually know to try and find (username,+inf) and walk backwards in-order).

In general, "covering indices" isn't a useful technique with Postgresql like it is with other databases, due to Postgresql's need to refer to the heap tuples for visibility information.

Upvotes: 1

Related Questions