Re: Pathify RHS unique-ification for semijoin planning
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Richard Guo <guofenglinux@gmail.com>,
Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-08-12T16:38:19Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Simplify relation_has_unique_index_for()
- bf9ee294e567 19 (unreleased) landed
-
Pathify RHS unique-ification for semijoin planning
- 24225ad9aafc 19 (unreleased) landed
-
Convert varatt.h access macros to static inline functions.
- e035863c9a04 19 (unreleased) cited
-
Re-export a few of createplan.c's make_xxx() functions.
- 570be1f73f38 9.6.0 cited
=?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de> writes: > No review, but apparently "uniquify" is more widely accepted than > "uniqueify". Personally I'd write "unique-ify", seeing that neither of the forms without the dash are considered good English. Of course, if you need to make identifiers out of this, that solution doesn't work; but you could just avoid the construction --- say, "make_path_unique" rather than "uniquify_path". regards, tom lane