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

2015-03-26 Thread Tomas Vondra
On 26.3.2015 17:35, Jeff Janes wrote: > On Thu, Mar 26, 2015 at 5:44 AM, Tomas Vondra > mailto:tomas.von...@2ndquadrant.com>> wrote: > >> That might work IMO, but maybe we should increase the coefficient a >> bit (say, from 1.25 to 2), not to produce needlessly long MCV >> lists. > > That wouldn'

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

2015-03-26 Thread Jeff Janes
On Thu, Mar 26, 2015 at 5:44 AM, Tomas Vondra wrote: > On 26.3.2015 08:48, Jeff Janes wrote: > > > > OK, this is starting to look like a long-standing bug to me. > > > > If it only sees 3 distinct values, and all three are present at least > > twice, it throws all of them into the MCV list. But i

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

2015-03-26 Thread Tomas Vondra
On 26.3.2015 08:48, Jeff Janes wrote: > > OK, this is starting to look like a long-standing bug to me. > > If it only sees 3 distinct values, and all three are present at least > twice, it throws all of them into the MCV list. But if one of those 3 > were present just once, then it tests them to s

[PERFORM] query faster with a foreign table

2015-03-26 Thread Dominique Vallée
Hello, I have an executing time problem for a query : this time is very different as I used a local table or a foreign table : 20 times faster for the foreign table On a server 9.4.1, I have 2 spatial bases b1 (size 5.4 Go) et b2 (size 19Mo) and in the base b1 the table tmp_obs_coordgps (61

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

2015-03-26 Thread Feike Steenbergen
Sorry, didn't respond to all your questions: > What version of PostgreSQL are running? 'select version();' PostgreSQL 9.3.4 on x86_64-pc-linux-gnu, compiled by gcc-4.6.real (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3, 64-bit > What do you get when to do "analyze verbose print_list"? # analyze verbose

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

2015-03-26 Thread Feike Steenbergen
On 25 March 2015 at 22:45, Jeff Janes 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 -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)

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

2015-03-26 Thread Jeff Janes
On Wed, Mar 25, 2015 at 1:00 PM, Feike Steenbergen < feikesteenber...@gmail.com> wrote: > On 25 March 2015 at 19:07, Jeff Janes wrote: > > > Also, I doubt that that is the problem in the first place. If you > collect a > > sample of 30,000 (which the default target size of 100 does), and the > >