David Rowley <dgrowleyml@gmail.com> writes:
> Unsure if such a feature is worthwhile. I think maybe not for just
> min(ctid)/max(ctid). However, there could be other reasons, such as
> the transform OR to UNION stuff that Tom worked on a few years ago.
> That needed to eliminate duplicate rows that matched both OR branches
> and that was done using ctid.
I'm kind of allergic to adding features that fundamentally depend on
ctid, seeing that there's so much activity around non-heap table AMs
that may not have any such concept, or may have a row ID that looks
totally different. (That's one reason why I stopped working on that
OR-to-UNION patch.)
regards, tom lane