Skip site navigation (1) Skip section navigation (2)

Re: Index Page Split logging

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Gokulakannan Somasundaram <gokul007(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Index Page Split logging
Date: 2008-01-02 10:40:02
Message-ID: 20080102104002.GC8566@svana.org (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Jan 02, 2008 at 04:04:48PM +0530, Gokulakannan Somasundaram wrote:
> On Jan 2, 2008 3:35 PM, Martijn van Oosterhout <kleptog(at)svana(dot)org> wrote:
> > If the goal is to only store the insert, then we need to determine
> > during recovery which page the record needs to be added to. To do this
> > you need to go through the index, which can only be done by calling
> > user-defined functions.
> 
> Correct me if i am wrong.
> User-defined functions act as comparison functions in GIST. But when do they
> act as comparison functions in b-tree? I am not able to understand exactly
> that part.

All indexes are done by user-defined functions, even b-trees. People can
make their own b-tree indexes by defining an operator class. Note that
"user-defined" is this case means anything called via the fmgr
interface.

For reference, hash indexes are defined by user-defined functions as
well... It's all about the intereaction between Index AMs and operator
classes.

Have a nice day,
-- 
Martijn van Oosterhout   <kleptog(at)svana(dot)org>   http://svana.org/kleptog/
> Those who make peaceful revolution impossible will make violent revolution inevitable.
>  -- John F Kennedy

In response to

Responses

pgsql-hackers by date

Next:From: Gokulakannan SomasundaramDate: 2008-01-02 11:16:11
Subject: Re: Index Page Split logging
Previous:From: Gokulakannan SomasundaramDate: 2008-01-02 10:34:48
Subject: Re: Index Page Split logging

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group