Re: Index only scan sometimes switches to sequential scan for small amount of rows

From: Feike Steenbergen <feikesteenbergen(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Index only scan sometimes switches to sequential scan for small amount of rows
Date: 2015-03-26 08:17:55
Message-ID: CAK_s-G1fH2Rv8K7i6vKRj1=xr6s3E1bJvFT7RcgEMz5BBAtgDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 25 March 2015 at 22:45, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:

> How can the avg_width be 4 when the vast majority of entries are 7
> characters long?

The datatype is an enum, as I understand it, an enum type always
occupies 4 bytes

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Feike Steenbergen 2015-03-26 08:26:11 Re: Index only scan sometimes switches to sequential scan for small amount of rows
Previous Message Jeff Janes 2015-03-26 07:48:34 Re: Index only scan sometimes switches to sequential scan for small amount of rows