Re: [PATCHES] GIN improvements

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] GIN improvements
Date: 2008-07-25 07:48:24
Message-ID: 48898548.8050603@sigaev.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> (a) that's not back-patchable and (b) it'll create a merge conflict with
> your patch, if you're still going to add a new AM function column.
> I think that aminsertcleanup per se isn't needed, but if we want an
> "amanalyze" there'd still be a conflict. Where are we on that?

I'll revert aminsertcleanup framework but leave gininsertcleanup function as is,
because I'll not have enough time until end of summer - I'd like to finalize
patch and fixes first.

--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message daveg 2008-07-25 07:52:23 Re: Additional psql requirements
Previous Message Zdenek Kotala 2008-07-25 07:45:20 Re: Review: DTrace probes (merged version) ver_03

Browse pgsql-patches by date

  From Date Subject
Next Message Simon Riggs 2008-07-25 19:46:18 Re: [PATCHES] odd output in restore mode
Previous Message Tatsuo Ishii 2008-07-25 00:26:52 Re: [PATCHES] WITH RECUSIVE patches 0723