pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hannu Krosing <hannu@tm.ee>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: marty@outputservices.com
Cc: herve@elma.fr
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Wed, 26 Jan 2005 10:17:43 -0500
Message-ID: <14870.1106752663@sss.pgh.pa.us> (raw)
In-Reply-To: <1106732479.5587.4.camel@fuji.krosing.net>
References: <41F144FE.30902@outputservices.com>
	<41F14758.4030602@outputservices.com>
	<20050122.121300.41631131.t-ishii@sra.co.jp>
	<25335.1106428223@sss.pgh.pa.us>
	<1106511352.31592.112.camel@localhost.localdomain>
	<6346.1106512803@sss.pgh.pa.us>
	<1106531786.5790.9.camel@fuji.krosing.net>
	<3582.1106667713@sss.pgh.pa.us>
	<1106732479.5587.4.camel@fuji.krosing.net>

Hannu Krosing <hannu@tm.ee> writes:
> But can't clearing up the index be left for "later" ? 

Based on what?  Are you going to store the information about what has to
be cleaned up somewhere else, and if so where?

> Indexscan has to check the data tuple anyway, at least for visibility.
> would adding the check for field sameness in index and data tuples be
> too big performance hit ?

It does pretty much suck, especially when you think about functional
indexes on expensive functions.

			regards, tom lane



view thread (131+ messages)  latest in thread

Message-ID: <14870.1106752663@sss.pgh.pa.us>
Permalink:  ../14870.1106752663@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/14870.1106752663@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, hannu@tm.ee, simon@2ndquadrant.com, t-ishii@sra.co.jp, marty@outputservices.com, herve@elma.fr
  Subject: Re: PostgreSQL clustering VS MySQL clustering
  In-Reply-To: <14870.1106752663@sss.pgh.pa.us>

* 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