Re: [PATCH] Use ssup_datum_*_cmp for int2, oid, and oid8 sort support

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: John Naylor <johncnaylorls(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Use ssup_datum_*_cmp for int2, oid, and oid8 sort support
Date: 2026-07-23 19:15:25
Message-ID: CAN4CZFNKHGuW=wZTsxSB+d8cb7ubtAt+d_6nC+HVz+KNVmEW9Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I think the easiest fix is to revert the oid part of commit 51cd5d6f0,
> leaving behind the int2 and oid8 parts. The asymmetry between the 2
> oid types would look odd, though, so that would require an explanatory
> comment.

Yes, that was my conclusion too, but I wanted to leave the decision up
to you and Baji Shaik.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2026-07-23 19:17:49 Skip redundant DISTINCT enforcement (setop branches, provably-unique input)
Previous Message surya poondla 2026-07-23 18:59:33 Re: [DESIGN] Soft DROP TABLE, recoverable drops for PostgreSQL