Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Postgres 11 chooses seq scan instead of index-only scan
From: twoflower <standa.kurik@xxxxxxxxx>
Date: Thu, 24 Jan 2019 08:01:18 -0700 (MST)
In-reply-to: <16149.1548341096@sss.pgh.pa.us>
References: <1548339807217-0.post@n3.nabble.com> <16149.1548341096@sss.pgh.pa.us>

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.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Postgres 11 chooses seq scan instead of index-only scan
  - From: Don Seiler

References:
- Postgres 11 chooses seq scan instead of index-only scan
  - From: twoflower
- Re: Postgres 11 chooses seq scan instead of index-only scan
  - From: Tom Lane

Prev by Date: Re: Postgres 11 chooses seq scan instead of index-only scan
Next by Date: Re: Casting Integer to Boolean in assignment
Previous by thread: Re: Postgres 11 chooses seq scan instead of index-only scan
Next by thread: Re: Postgres 11 chooses seq scan instead of index-only scan
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux