Re: Mark/Restore and avoiding RandomAccess sorts - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Mark/Restore and avoiding RandomAccess sorts
Date
Msg-id 7225.1168441827@sss.pgh.pa.us
Whole thread Raw
In response to Mark/Restore and avoiding RandomAccess sorts  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: Mark/Restore and avoiding RandomAccess sorts  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-hackers
"Simon Riggs" <simon@2ndquadrant.com> writes:
> Merge Joins require us to potentially Mark and Restore positions in the
> tuples arriving from executor sub-nodes.

I came across an old note to myself suggesting that we handle this by
interposing a Materialize node, and then teaching Material that if it's
told EXEC_FLAG_MARK but not EXEC_FLAG_REWIND or EXEC_FLAG_BACKWARD, it
need keep data only as far back as the Mark position.  So the structural
requirements are mostly in place already, it's just a matter of figuring
out a nice way to implement the "drop older parts of the tuplestore"
business.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Operator family docs
Next
From: "Simon Riggs"
Date:
Subject: Re: [PATCHES] COPY with no WAL, in certain circumstances