pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Andrea Arcangeli <andrea@cpushare.com>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Matteo Beccati <php@beccati.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: NOT LIKE much faster than LIKE?
Date: Wed, 11 Jan 2006 10:18:41 +0100
Message-ID: <20060111091841.GA15897@opteron.random> (raw)
In-Reply-To: <1136970465.21025.527.camel@localhost.localdomain>
References: <24021.1136858688@sss.pgh.pa.us>
	<20060110022303.GA20168@opteron.random>
	<24372.1136861684@sss.pgh.pa.us>
	<43C3799D.5030103@beccati.com>
	<1625.1136915395@sss.pgh.pa.us>
	<1136930796.21025.486.camel@localhost.localdomain>
	<6398.1136931685@sss.pgh.pa.us>
	<1136936205.21025.507.camel@localhost.localdomain>
	<7924.1136950830@sss.pgh.pa.us>
	<1136970465.21025.527.camel@localhost.localdomain>

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.

view thread (26+ messages)  latest in thread

Message-ID: <20060111091841.GA15897@opteron.random>
Permalink:  ../20060111091841.GA15897@opteron.random/
Also on:    postgresql.org/message-id/20060111091841.GA15897@opteron.random

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: andrea@cpushare.com, simon@2ndquadrant.com, tgl@sss.pgh.pa.us, php@beccati.com
  Subject: Re: NOT LIKE much faster than LIKE?
  In-Reply-To: <20060111091841.GA15897@opteron.random>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox