Silvio Matthes <silvio(dot)matthes(at)xcom(dot)de> writes:
> But in my opinion with the multicolumn index in mind the server should do 
> a index scan, because there are only 7 rows with param_name='KUNDEN_NR' 
> and param_value=''?!?

We do not have any cross-column statistics at the moment, so the planner
is unable to recognize the potential win here.  Note the poor estimate
of the number of matching rows in your EXPLAIN result.

I think though that it might help to put param_name first in the
multicolumn index.

			regards, tom lane

In response to

• Re: select ... where <column>='' does a seqscan [auf Viren at 2004-08-24 16:34:03 from Silvio Matthes

Responses

• Re: select ... where <column>='' does a seqscan [auf at 2004-08-25 08:23:20 from Silvio Matthes

pgsql-general by date

Next:	From: Tom Lane	Date: 2004-08-24 16:55:53
	Subject: Re: WG: Re: Re: select ... where <column>='' does a seqscan [auf Viren geprueft]
Previous:	From: Tom Lane	Date: 2004-08-24 16:43:44
	Subject: Re: pg_stat_activity versus ps