> Perhaps instead
> of storing each and every trigger-related tuple in memory, we only need
> to store one value per affected table: the lowest CTID of any tuple
> that we need to revisit for deferred-trigger purposes. At the end of
> the transaction, scan forward from that point to the end of the table,
> looking for tuples that were inserted by the current xact.
I thought that this current placing of new rows at end of file is subject to
change soon (overwrite smgr) ?
I thus think it would be better to remember all ctids per table.
The rest imho sounds great.
Andreas
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
