Hitoshi Harada <[email protected]> writes:
> Looking for git/cvs log a bit, tuplesort was already there since 1999
> while tuplestore was introduced around 2000 for materialized node. Why
> then was tuplestore invented as a new feature instead of extending
> tuplesort? Can't we unit them now?
I think they'd be unmaintainable if merged. Each one is complicated
enough as-is, and they have different concerns and different use-cases
to optimize for. Moreover it's not clear that merging them would buy us
much --- saving one copy step doesn't excite me, even if it actually
came out to be true which I'm unconvinced about.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
