Greg Stark <gsst...@mit.edu> writes: > There was some discussion of doing this in general for all inserts > inside the indexam. The btree indexam could buffer up any inserts done > within the transaction and keep them in an in-memory btree. Any > lookups done within the transaction first look up in the in-memory > tree then the disk. If the in-memory buffer fills up then we flush > them to the index.
> The reason this is tempting is that we could then insert them all in a > single index-merge operation which would often be more efficient than > retail inserts. That's not gonna work for a unique index, which unfortunately is a pretty common case ... regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers