Re: Postgres 11 chooses seq scan instead of index-only scan

From: twoflower <standa(dot)kurik(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgres 11 chooses seq scan instead of index-only scan
Date: 2019-01-24 15:01:18
Message-ID: 1548342078079-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Geoff Winkless 2019-01-24 15:05:35 Re: Casting Integer to Boolean in assignment
Previous Message Tom Lane 2019-01-24 14:44:56 Re: Postgres 11 chooses seq scan instead of index-only scan