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

From Tom Lane
Subject Re: Postgres 11 chooses seq scan instead of index-only scan
Date
Msg-id 16149.1548341096@sss.pgh.pa.us
Whole thread Raw
In response to Postgres 11 chooses seq scan instead of index-only scan  (twoflower <standa.kurik@gmail.com>)
Responses Re: Postgres 11 chooses seq scan instead of index-only scan
List pgsql-general
twoflower <standa.kurik@gmail.com> writes:
> One issue I cannot resolve is the new server using a parallel seq scan
> instead of index-only scan for the following query:
> select count(id) from history_translation

You might need to vacuum the table to ensure that the planner thinks
a reasonable proportion of the pages are all-visible (see
pg_class.relallvisible).

            regards, tom lane


pgsql-general by date:

Previous
From: Hellmuth Vargas
Date:
Subject: Re: How duplicate values inserted into the primary key column oftable and how to fix it
Next
From: twoflower
Date:
Subject: Re: Postgres 11 chooses seq scan instead of index-only scan