Dimitri Fontaine <[email protected]> writes:
> Tom Lane <[email protected]> writes:
>> So to fix these problems we'd need to replace sort operator OIDs in
>> SortGroupClause and plan nodes with those three items. Obviously, this
>> would be slightly bulkier, but the extra cost added to copying parse and
>> plan trees should be tiny compared to the avoided syscache lookups.
> My understanding is that opfamily+datatype gives an opclass. What about
> storing the opclass OID there?
Then you'd just need to look up the opfamily again. Opclasses are too
small a division to be useful.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
