Re: [PERFORM] row estimate very wrong for array type

2011-05-04 Thread Denis de Bernardy
> - Original Message - >> From: Tom Lane >> To: Denis de Bernardy >> Cc: "pgsql-performance@postgresql.org" > >> Sent: Wednesday, May 4, 2011 4:12 PM >> Subject: Re: [PERFORM] row estimate very wrong for array type >> >>

Re: [PERFORM] row estimate very wrong for array type

2011-05-04 Thread Denis de Bernardy
y, May 4, 2011 4:12 PM > Subject: Re: [PERFORM] row estimate very wrong for array type > > Denis de Bernardy writes: >> [ estimates for array && suck ] >> Might this be a bug in the operator's selectivity, or am I doing > something wrong? > > Array

Re: [PERFORM] row estimate very wrong for array type

2011-05-04 Thread Tom Lane
Denis de Bernardy writes: > [ estimates for array && suck ] > Might this be a bug in the operator's selectivity, or am I doing something > wrong? Array && uses areasel() which is only a stub :-( In the particular case here it'd be possible to get decent answers just by trying the operator again

[PERFORM] row estimate very wrong for array type

2011-05-04 Thread Denis de Bernardy
Hi, I'm running into erroneous row estimates when using an array type, and I'm running out of ideas on how to steer postgres into the right direction... I've tried setting statistics to 1000, vacuuming and analyzing over and over, rewriting the query differently... to no avail. The table looks