Thread: pgsql: Make a couple of small changes to the tuplestore API, for the
pgsql: Make a couple of small changes to the tuplestore API, for the
From
tgl@postgresql.org (Tom Lane)
Date:
Log Message: ----------- Make a couple of small changes to the tuplestore API, for the benefit of the upcoming window-functions patch. First, tuplestore_trim is now an exported function that must be explicitly invoked by callers at appropriate times, rather than something that tuplestore tries to do behind the scenes. Second, a read pointer that is marked as allowing backward scan no longer prevents truncation. This means that a read pointer marked as having BACKWARD but not REWIND capability can only safely read backwards as far as the oldest other read pointer. (The expected use pattern for this involves having another read pointer that serves as the truncation fencepost.) Modified Files: -------------- pgsql/src/backend/executor: nodeMaterial.c (r1.63 -> r1.64) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/nodeMaterial.c?r1=1.63&r2=1.64) pgsql/src/backend/utils/sort: tuplestore.c (r1.43 -> r1.44) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/sort/tuplestore.c?r1=1.43&r2=1.44) pgsql/src/include/utils: tuplestore.h (r1.25 -> r1.26) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/tuplestore.h?r1=1.25&r2=1.26)