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

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Teodor Sigaev <teodor@sigaev.ru>
Cc: Oleg Bartunov <oleg@sai.msu.su>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [PATCHES] GIN improvements
Date: Wed, 23 Jul 2008 11:05:35 -0400
Message-ID: <15378.1216825535@sss.pgh.pa.us> (raw)
In-Reply-To: <488734A5.9030503@sigaev.ru>
References: <483FD205.4090904@sigaev.ru>
	<486BC501.6060605@sigaev.ru>
	<27880.1215810535@sss.pgh.pa.us>
	<487A6E0C.3090600@sigaev.ru>
	<29437.1216742605@sss.pgh.pa.us>
	<48861758.4070507@sigaev.ru>
	<1636.1216749010@sss.pgh.pa.us>
	<488625E8.4070203@sigaev.ru>
	<2818.1216753264@sss.pgh.pa.us>
	<488734A5.9030503@sigaev.ru>

Teodor Sigaev <teodor@sigaev.ru> writes:
> So, may be we just move insertcleanup call to   ginbulkdelete/ginvacuumcleanup 
> but leave aminsertcleanup field in pg_proc for a future.

I'd be inclined not to add the extra AM call if we aren't going to use
it now.  There's no very good reason to think that a definition we
settled on today would be exactly the right thing for whatever future
need might appear.  Better to wait till we have a concrete example to
design around.

			regards, tom lane



view thread (74+ messages)  latest in thread

Message-ID: <15378.1216825535@sss.pgh.pa.us>
Permalink:  ../15378.1216825535@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/15378.1216825535@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-patches@postgresql.org
  Cc: tgl@sss.pgh.pa.us, teodor@sigaev.ru, oleg@sai.msu.su, pgsql-hackers@postgresql.org
  Subject: Re: [PATCHES] GIN improvements
  In-Reply-To: <15378.1216825535@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