Re: Postgres 11 chooses seq scan instead of index-only scan - Mailing list pgsql-general

From twoflower
Subject Re: Postgres 11 chooses seq scan instead of index-only scan
Date
Msg-id 1548342078079-0.post@n3.nabble.com
Whole thread Raw
In response to Re: Postgres 11 chooses seq scan instead of index-only scan  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Postgres 11 chooses seq scan instead of index-only scan  (Don Seiler <don@seiler.us>)
List pgsql-general
Yes! That was it, after running VACUUM TABLE history_translation, the query is now executed using index-only scan.

I was under the impression that ANALYZE TABLE history_translation is enough, but it is not.

Thank you very much.

Sent from the PostgreSQL - general mailing list archive at Nabble.com.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgres 11 chooses seq scan instead of index-only scan
Next
From: Geoff Winkless
Date:
Subject: Re: Casting Integer to Boolean in assignment