James William Pye <[EMAIL PROTECTED]> writes:
> The problem with the AM no longer having the ability to make guarantees about
> lock/state duration seems more or less unavoidable with this two-step process.
So in other words, a two-step process is wrong.
> Besides that I think it's ready for revi
Ok. Here's a `gmake check` passing version that actually makes use of the new
AM entries in ExecInsert. Currently, AFAICS, this *only* provides an improvement
for systems that frequently insert duplicate rows. Perhaps not a common case,
but an improvement nonetheless, IMO.
I leaned in this directi
