Re: SQL:2011 application time
Peter Eisentraut <peter@eisentraut.org>
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
On 02.11.23 21:21, Paul Jungwirth wrote: > New patches attached (rebased to 0bc726d9). I went over the patch v17-0001-Add-temporal-PRIMARY-KEY-and-UNIQUE-constraints.patch in more detail. Attached is a fixup patch that addresses a variety of cosmetic issues. Some details: - Renamed contemporal to conwithoutoverlaps, as previously discussed. Also renamed various variables and function arguments similarly. - Rearranged text in CREATE TABLE reference page so there are no forward references. (Describe WITHOUT OVERLAPS under UNIQUE and then PRIMARY KEy says "see above", rather than describe it under PRIMARY KEY and have UNIQUE say "see below.) - Removed various bits that related to temporal foreign keys, which belong in a later patch. - Reverted some apparently unrelated changes in src/backend/catalog/index.c. - Removed the "temporal UNIQUE" constraint_type assignment in DefineIndex(). This is meant to be used in error messages and should refer to actual syntax. I think it's fine without it this change. - Field contemporal in NewConstraint struct is not used by this patch. - Rearrange the grammar so that the rule with WITHOUT OVERLAPS is just a Boolean attribute rather than column name plus keywords. This was kind of confusing earlier and led to weird error messages for invalid syntax. I kept the restriction that you need at least one non-overlaps column, but that is now enforced in parse analysis, not in the grammar. (But maybe we don't need it?) (After your earlier explanation, I'm content to just allow one WITHOUT OVERLAPS column for now.) - Some places looked at conexclop to check whether something is a WITHOUT OVERLAPS constraint, instead of looking at conwithoutoverlaps directly. - Removed some redundant "unlike" entries in the pg_dump tests. (This caused cfbot tests to fail.) - Moved the "without_overlaps" test later in the schedule. It should at least be after "constraints" so that normal constraints are tested first. Two areas that could be improved: 1) In src/backend/commands/indexcmds.c, get_index_attr_temporal_operator() has this comment: + * This seems like a hack + * but I can't find any existing lookup function + * that knows about pseudotypes. This doesn't see very confident. ;-) I don't quite understand this. Is this a gap in the currently available APIs, do we need to improve something here, or does this need more research? 2) In src/backend/parser/parse_utilcmd.c, transformIndexConstraint(), there is too much duplication between the normal and the if (constraint->without_overlaps) case, like the whole not-null constraints stuff at the end. This should be one code block with a few conditionals inside. Also, the normal case deals with things like table inheritance, which the added parts do not. Is this all complete? I'm not sure the validateWithoutOverlaps() function is needed at this point in the code. We just need to check that the column exists, which the normal code path already does, and then have the index creation code later check that an appropriate overlaps operator exists. We don't even need to restrict this to range types. Consider for example, it's possible that a type does not have a btree equality operator. We don't check that here either, but let the index code later check it. Overall, with these fixes, I think this patch is structurally okay. We just need to make sure we have all the weird corner cases covered.