pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dmitry Tkach <dmitry@openratings.com>
To: pgsql-general@postgresql.org.pgsql-sql
Subject: A bug in gistPageAddItem()/gist_tuple_replacekey() ???
Date: Thu, 21 Mar 2002 16:33:31 -0500
Message-ID: <3C9A51AB.5040301@openratings.com> (raw)

I was trying to write a gist index extension, and, after some debugging, 
it looks like I found a bug somewhere in the gist.c code ...
I can't be quite sure, because I am not familiar with the postgres 
code... but, here is what I see happenning (this is 7.1, but I compared 
the sources to 7.2, and did not see this fixed - although, I did not 
inspect it too carefully)...

First of all, gistPageAddItem () calls gistdentryinit() with a pointer 
to what's stored in the tuple, so, 'by-value' types do not work (because 
gistcentryinit () would be passed the value itself, when called from 
gistinsert(), and then, in gistPageAddItem (), it is passed a pointer, 
coming from gistdentryinit () - so, it just doesn't know really how to 
treat the argument)...

Secondly, gist_tuple_replacekey() seems to have incorrect logic figuring 
out if there is enough space in the tuple (it checks for '<', instead of 
'<=') - this causes a new tuple to get always created (this one, seems 
to be fixed in 7.2)

Thirdly, gist_tuple_replace_key () sends a pointer to entry.pred (which 
is already a pointer to the actual value) to index_formtuple (), that 
looks at the tuple, sees that the type is 'pass-by-value', and puts that 
pointer directly into the tuple, so that, the resulting tuple now 
contains a pointer to a pointer to the actual value...

Now, if more then one split is required, this sequence is repeated again 
and again and again, so that, by the time the tuple gets actually 
written, it contains something like a pointer to a pointer to a pointer 
to a pointer to the actual data :-(

Once again, I've seen some comments in the 7.2 branch about gists and 
pass-by-value types, but brief looking at the differences in the source 
did not make me conveinced that it was indeed fixed...

Anyone knows otherwise?

Thanks a lot!

Dima




view thread (2+ messages)  latest in thread

Message-ID: <3C9A51AB.5040301@openratings.com>
Permalink:  ../3C9A51AB.5040301@openratings.com/
Also on:    postgresql.org/message-id/3C9A51AB.5040301@openratings.com

 · 

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-sql@postgresql.org
  Cc: dmitry@openratings.com, pgsql-general@postgresql.org.pgsql-sql
  Subject: Re: A bug in gistPageAddItem()/gist_tuple_replacekey() ???
  In-Reply-To: <3C9A51AB.5040301@openratings.com>

* 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