pg.ddx.io  pgsql-patches@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Teodor Sigaev <teodor@sigaev.ru>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Patches <pgsql-patches@postgresql.org>
Subject: Re: GIN improvements
Date: Tue, 10 Jun 2008 15:38:21 +0400
Message-ID: <484E67AD.7020500@sigaev.ru> (raw)
In-Reply-To: <20080608224649.GC11028@alvh.no-ip.org>
References: <483FD205.4090904@sigaev.ru>
	<4849418C.6080909@sigaev.ru>
	<20080608224649.GC11028@alvh.no-ip.org>

> Right now this is not a problem because there is no insert_cleanup
> function for btree, but I wonder if we should clean it up.
Look at gistbulkdelete and gistvacuumcleanup, first function wants to send a 
bool flag to second one and they use GiSTBulkDelete structure instead of usual 
IndexBulkDeleteResult. When it will be needed btree may use the same method.

> 
> FWIW there's a typo in catalogs.sgml (finction -> function)
Thank you, will fix.

> What's the use of the FASTUPDATE parameter?  Is there a case when a user
> is interested in turning it off?

Yeah - when time of search is much-much more important (or crucial)  than 
insertion time. Or table stores read-only values.

-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
                                                    WWW: http://www.sigaev.ru/



view thread (74+ messages)  latest in thread

Message-ID: <484E67AD.7020500@sigaev.ru>
Permalink:  ../484E67AD.7020500@sigaev.ru/
Also on:    postgresql.org/message-id/484E67AD.7020500@sigaev.ru

 · 

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-patches@postgresql.org
  Cc: teodor@sigaev.ru, alvherre@commandprompt.com
  Subject: Re: GIN improvements
  In-Reply-To: <484E67AD.7020500@sigaev.ru>

* 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