Re: Why we have tuplestore and tuplesort? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Why we have tuplestore and tuplesort?
Date
Msg-id 17605.1250363972@sss.pgh.pa.us
Whole thread Raw
In response to Why we have tuplestore and tuplesort?  (Hitoshi Harada <umi.tanuki@gmail.com>)
Responses Re: Why we have tuplestore and tuplesort?  (Hitoshi Harada <umi.tanuki@gmail.com>)
List pgsql-hackers
Hitoshi Harada <umi.tanuki@gmail.com> 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


pgsql-hackers by date:

Previous
From: Hitoshi Harada
Date:
Subject: Why we have tuplestore and tuplesort?
Next
From: Hitoshi Harada
Date:
Subject: Re: Why we have tuplestore and tuplesort?