Re: SQL:2011 application time
Paul A Jungwirth <pj@illuminatedcomputing.com>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Rename gist stratnum support function
- 32edf732e8dc 18.0 landed
-
Remove support for temporal RESTRICT foreign keys
- b83e8a2ca2eb 18.0 landed
-
Cache NO ACTION foreign keys separately from RESTRICT foreign keys
- 9926f854d077 18.0 landed
-
Fix NO ACTION temporal foreign keys when the referenced endpoints change
- 1772d554b089 18.0 landed
-
Improve whitespace in without_overlaps test
- 888d4523f0c2 18.0 landed
-
Tests for logical replication with temporal keys
- 939b0908c87a 18.0 landed
-
Support for GiST in get_equal_strategy_number()
- 74edabce7a33 18.0 landed
-
Make the conditions in IsIndexUsableForReplicaIdentityFull() more explicit
- 13544e790ef8 18.0 landed
-
Replace get_equal_strategy_number_for_am() by get_equal_strategy_number()
- a2a475b011cf 18.0 landed
-
Improve internal logical replication error for missing equality strategy
- 321c287351f7 18.0 landed
-
Simplify IsIndexUsableForReplicaIdentityFull()
- 7727049e8f66 18.0 landed
-
Fix ALTER TABLE / REPLICA IDENTITY for temporal tables
- 79b575d3bc09 18.0 landed
-
doc: Update pg_constraint.conexclop docs for WITHOUT OVERLAPS
- f683ba0867da 18.0 landed
-
doc: Add PERIOD to ALTER TABLE reference docs
- d56af4c882e2 18.0 landed
-
doc: Add WITHOUT OVERLAPS to ALTER TABLE reference docs
- bf621059500b 18.0 landed
-
Add temporal FOREIGN KEY contraints
- 89f908a6d0ac 18.0 landed
- 34768ee36165 17.0 landed
-
Add temporal PRIMARY KEY and UNIQUE constraints
- fc0438b4e805 18.0 landed
- 46a0cd4cefb4 17.0 landed
-
Add stratnum GiST support function
- 7406ab623fee 18.0 landed
- 6db4598fcb82 17.0 landed
-
Avoid crashing when a JIT-inlined backend function throws an error.
- 5d6c64d29097 17.0 cited
-
Revert temporal primary keys and foreign keys
- 8aee330af55d 17.0 landed
-
Fix ON CONFLICT DO NOTHING/UPDATE for temporal indexes
- 144c2ce0cc75 17.0 landed
-
Add test for REPLICA IDENTITY with a temporal key
- 482e108cd38d 17.0 landed
-
Use half-open interval notation in without_overlaps tests
- 5577a71fb0cc 17.0 landed
-
Use daterange and YMD in without_overlaps tests instead of tsrange.
- a88c800deb6f 17.0 landed
-
Rename pg_constraint.conwithoutoverlaps to conperiod
- 030e10ff1a36 17.0 landed
-
Fix comment on gist_stratnum_btree
- 86232a49a437 17.0 landed
-
Add missing TAP test name
- 1ab763fc22ad 16.0 cited
-
Improve error handling of HMAC computations
- 5513dc6a304d 15.0 cited
-
Rename functions to avoid future conflicts
- ee419607381d 15.0 landed
Attachments
- v8-0001-Add-PERIODs.patch (application/octet-stream) patch v8-0001
- v8-0002-Add-temporal-PRIMARY-KEY-and-UNIQUE-constraints.patch (application/octet-stream) patch v8-0002
- v8-0003-Add-UPDATE-DELETE-FOR-PORTION-OF.patch (application/octet-stream) patch v8-0003
- v8-0004-Add-temporal-FOREIGN-KEYs.patch (application/octet-stream) patch v8-0004
On Fri, Sep 10, 2021 at 6:50 PM Jaime Casanova <jcasanov@systemguards.com.ec> wrote: > > patch 01: does apply but gives a compile warning (which is fixed by patch > 02) > [snip] > patch 03: produces these compile errors. I did a rebase and fixed this new error, as well as the warnings. On Mon, Sep 6, 2021 at 1:40 PM Zhihong Yu <zyu@yugabyte.com> wrote: > > + * Portions Copyright (c) 1996-2018, PostgreSQL Global Development Group > > It seems the year (2018) should be updated to 2021. Done. > For RemovePeriodById(), it seems table_open() can be called after SearchSysCache1(). This way, if HeapTupleIsValid(tup) is true, table_open() can be skipped. This seems like it permits a race condition when two connections both try to drop the period, right? > For tablecmds.c, AT_PASS_ADD_PERIOD is defined as 5 with AT_PASS_ADD_CONSTR etc moved upward. Do we need to consider compatibility ? I don't think there is a compatibility problem---can you explain? These symbols aren't used outside tablecmds.c and the values aren't saved anywhere AFAIK. > There are a few TODO's such as: > Are they going to be addressed in the next round of patches ? These are mostly questions I'm hoping a reviewer can help me answer, but I'll take a pass through them and see which I can remove myself. Several are for adding support for partitioned tables, where I would definitely appreciate help. > There seems to be some overlap between ATExecAddPeriod() and AddRelationNewPeriod(). > Is it possible to reduce code duplication ? I've refactored those functions to remove some duplication, but I think I prefer the old version---let me know if you have suggestions to avoid the duplication in a nicer way. Oh also I realized fp_triggers.c wasn't included in the last few patch files---I'm sorry about that! Latest files attached. Thanks for the reviews! Paul