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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: twoflower <standa(dot)kurik(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Postgres 11 chooses seq scan instead of index-only scan
Date: 2019-01-24 14:44:56
Message-ID: 16149.1548341096@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

twoflower <standa(dot)kurik(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message twoflower 2019-01-24 15:01:18 Re: Postgres 11 chooses seq scan instead of index-only scan
Previous Message Hellmuth Vargas 2019-01-24 14:43:11 Re: How duplicate values inserted into the primary key column of table and how to fix it