Horton

Re: SQL:2011 application time

Peter Eisentraut <peter@eisentraut.org>

View thread
From: Peter Eisentraut <peter@eisentraut.org>
To: Paul Jungwirth <pj@illuminatedcomputing.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-05-26T05:57: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 →

  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

Attachments

On 17.09.24 11:45, Peter Eisentraut wrote:
> On 05.09.24 14:09, Peter Eisentraut wrote:
>> On 07.08.24 22:54, Paul Jungwirth wrote:
>>> Here are some fixes based on outstanding feedback (some old some new). 
>>
>> I have studied your patches v39-0001 through v39-0004, which 
>> correspond to what had been reverted plus the new empty range check 
>> plus various minor fixes.  This looks good to me now, so I propose to 
>> go ahead with that.
>>
>> Btw., in your 0003 you point out that this prevents using the WITHOUT 
>> OVERLAPS functionality for non-range types.  But I think this could be 
>> accomplished by adding an "is empty" callback as a support function or 
>> something like that.  I'm not suggesting to do that here, but it might 
>> be worth leaving a comment about that possibility.
> 
> I have committed these, as explained here.

Here we added a gist support function that we internally refer to by the 
symbol GIST_STRATNUM_PROC.  This translated from "well-known" strategy 
numbers to opfamily-specific strategy numbers.  However, we later 
changed this to fit into index-AM-level compare type mapping, so this 
function actually now maps from compare type to opfamily-specific 
strategy numbers.  So I'm wondering if this name is still good.

Moreover, the index AM level also supports the opposite, a function to 
map from strategy number to compare type.  This is currently not 
supported in gist, but one might wonder what this function is supposed 
to be called when it is added.

So I went through and updated the naming of the gist-level functionality 
to be more in line with the index-AM-level functionality; see attached 
patch.  I think this makes sense because these are essentially the same 
thing on different levels.  What do you think?  (This would be for PG18.)