Horton

Re: SQL:2011 application time

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: Paul A Jungwirth <pj@illuminatedcomputing.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-06-02T13:50:45Z
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 →

  1. Rename gist stratnum support function

  2. Remove support for temporal RESTRICT foreign keys

  3. Cache NO ACTION foreign keys separately from RESTRICT foreign keys

  4. Fix NO ACTION temporal foreign keys when the referenced endpoints change

  5. Improve whitespace in without_overlaps test

  6. Tests for logical replication with temporal keys

  7. Support for GiST in get_equal_strategy_number()

  8. Make the conditions in IsIndexUsableForReplicaIdentityFull() more explicit

  9. Replace get_equal_strategy_number_for_am() by get_equal_strategy_number()

  10. Improve internal logical replication error for missing equality strategy

  11. Simplify IsIndexUsableForReplicaIdentityFull()

  12. Fix ALTER TABLE / REPLICA IDENTITY for temporal tables

  13. doc: Update pg_constraint.conexclop docs for WITHOUT OVERLAPS

  14. doc: Add PERIOD to ALTER TABLE reference docs

  15. doc: Add WITHOUT OVERLAPS to ALTER TABLE reference docs

  16. Add temporal FOREIGN KEY contraints

  17. Add temporal PRIMARY KEY and UNIQUE constraints

  18. Add stratnum GiST support function

  19. Avoid crashing when a JIT-inlined backend function throws an error.

  20. Revert temporal primary keys and foreign keys

  21. Fix ON CONFLICT DO NOTHING/UPDATE for temporal indexes

  22. Add test for REPLICA IDENTITY with a temporal key

  23. Use half-open interval notation in without_overlaps tests

  24. Use daterange and YMD in without_overlaps tests instead of tsrange.

  25. Rename pg_constraint.conwithoutoverlaps to conperiod

  26. Fix comment on gist_stratnum_btree

  27. Add missing TAP test name

  28. Improve error handling of HMAC computations

  29. Rename functions to avoid future conflicts

Peter Eisentraut <peter@eisentraut.org> writes:
> On 26.05.25 23:18, Paul A Jungwirth wrote:
>> Here do we want to say "respective operator class" instead of
>> "respective operator family"? Or "operator class/family"? Technically
>> btree_gist attaches it to the whole opfamily, but that's only because
>> there is no appropriate ALTER OPERATOR CLASS functionality:

> Thanks, I have committed it as is.  The function is part of the operator 
> family; I guess there could be different interpretations about why that 
> is so, but I think this would introduce more confusion if we somehow 
> talked about operator classes in this context.

GIST and GIN have traditionally not made any distinction between
operator classes and families: they're always one-class-per-family.
I guess that's because they cater more to one-off opclasses where
there is not meaningful commonality of semantics across opclasses,
nor the possibility of operators belonging to multiple opclasses.

That being the case, I'm hesitant to spend a lot of time worrying
about whether particular behavior belongs at the class or family
level.  Without concrete examples to look at, there's little hope
of getting it right anyway.  So I'm content with Peter's choice
here.  Perhaps sometime in the future we will have useful examples
with which to revisit this question.

[ wanders away wondering about recasting btree_gist and btree_gin
as single opfamilies ... ]

			regards, tom lane