Simon Riggs <si...@2ndquadrant.com> writes:
> On 28 February 2017 at 13:05, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> Um ... isn't there a transaction boundary there anyway?
> Yes, the patch releases the snapshot early, so it does not hold it
> once the build scan has completed. This allows the sort and build
> phases to occur without holding back the xmin.
Oh ... so Alvaro explained it badly. The reason this is specific to
btree is that it's the only AM with any significant post-scan building
time.
However, now that I read the patch: this is a horribly ugly hack.
I really don't like the API (if it even deserves the dignity of that
name) that you've added to snapmgr. I supposwe the zero documentation
for it fits in nicely with the fact that it's a badly-thought-out kluge.
I think it would be better to just move the responsibility for snapshot
popping in this sequence to the index AMs, full stop.
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
