Re: NOT LIKE much faster than LIKE?

From: Andrea Arcangeli <andrea(at)cpushare(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Matteo Beccati <php(at)beccati(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: NOT LIKE much faster than LIKE?
Date: 2006-01-11 09:18:41
Message-ID: 20060111091841.GA15897@opteron.random
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, Jan 11, 2006 at 09:07:45AM +0000, Simon Riggs wrote:
> I would suggest we do this only when all of these are true
> - when accessing more than one table, so the selectivity could effect a
> join result

FWIW my problem only happens if I join: on the main table where the
kernel_version string is stored (without joins), everything is always
blazing fast. So this requirement certainly sounds fine to me.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Alessandro Baretta 2006-01-11 09:42:45 Re: 500x speed-down: Wrong statistics!
Previous Message Simon Riggs 2006-01-11 09:07:45 Re: NOT LIKE much faster than LIKE?