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

help / color / mirror / Atom feed

From: Gregory Stark <stark@enterprisedb.com>
To: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jaime Casanova <systemguards@gmail.com>
Cc: PostgreSQL-patches <pgsql-patches@postgresql.org>
Subject: Re: Maintaining cluster order on insert
Date: Mon, 18 Jun 2007 09:49:28 +0100
Message-ID: <87wsy1hckn.fsf@oxford.xeocode.com> (raw)
In-Reply-To: <46761DB7.7070505@enterprisedb.com>
References: <200705152223.l4FMNJa17969@momjian.us>
	<464A33AB.1050401@enterprisedb.com>
	<20070516003810.GI20707@nasby.net>
	<464B15EF.4000808@enterprisedb.com>
	<c2d9e70e0705172153g3207adb6kd4abdfdf3a9215ff@mail.gmail.com>
	<464D96D6.1030608@enterprisedb.com>
	<c2d9e70e0705182205o44a4bbbft18a73b9de91de726@mail.gmail.com>
	<464F410C.8090900@enterprisedb.com>
	<10328.1182113758@sss.pgh.pa.us>
	<46761DB7.7070505@enterprisedb.com>

"Heikki Linnakangas" <heikki@enterprisedb.com> writes:

> The reason for switching to the new API instead of the amsuggestblock API is
> CPU overhead. It avoids constructing the IndexTuple twice and descending the
> tree twice.

I wonder if it's possible to finesse this. Have the suggestblock function
remember the last block it suggested and somehow recognize when it's given the
same tuple to index. Keeping the block pinned would still be the sticky point
though.


-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

view thread (46+ messages)  latest in thread

Message-ID: <87wsy1hckn.fsf@oxford.xeocode.com>
Permalink:  ../87wsy1hckn.fsf@oxford.xeocode.com/
Also on:    postgresql.org/message-id/87wsy1hckn.fsf@oxford.xeocode.com

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-hackers@postgresql.org
  Cc: stark@enterprisedb.com, heikki@enterprisedb.com, tgl@sss.pgh.pa.us, systemguards@gmail.com, pgsql-patches@postgresql.org
  Subject: Re: Maintaining cluster order on insert
  In-Reply-To: <87wsy1hckn.fsf@oxford.xeocode.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