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
I have committed the
v2-0001-Fix-ON-CONFLICT-DO-NOTHING-UPDATE-for-temporal-in.patch from
this (confusingly, there was also a v2 earlier in this thread), and I'll
continue working on the remaining items.
On 09.05.24 06:24, Paul Jungwirth wrote:
> Here are a couple new patches, rebased to e305f715, addressing Peter's
> feedback. I'm still working on integrating jian he's suggestions for the
> last patch, so I've omitted that one here.
>
> On 5/8/24 06:51, Peter Eisentraut wrote:
>> About v2-0001-Fix-ON-CONFLICT-DO-NOTHING-UPDATE-for-temporal-in.patch,
>> I think the
>> ideas are right, but I wonder if we can fine-tune the new conditionals
>> a bit.
>>
>> --- a/src/backend/executor/execIndexing.c
>> +++ b/src/backend/executor/execIndexing.c
>> @@ -210,7 +210,7 @@ ExecOpenIndices(ResultRelInfo *resultRelInfo, bool
>> speculative)
>> * If the indexes are to be used for speculative
>> insertion, add extra
>> * information required by unique index entries.
>> */
>> - if (speculative && ii->ii_Unique)
>> + if (speculative && ii->ii_Unique &&
>> !ii->ii_HasWithoutOverlaps)
>> BuildSpeculativeIndexInfo(indexDesc, ii);
>>
>> Here, I think we could check !indexDesc->rd_index->indisexclusion
>> instead. So we
>> wouldn't need ii_HasWithoutOverlaps.
>
> Okay.
>
>> Or we could push this into BuildSpeculativeIndexInfo(); it could just
>> skip the rest
>> if an exclusion constraint is passed, on the theory that all the
>> speculative index
>> info is already present in that case.
>
> I like how BuildSpeculativeIndexInfo starts with an Assert that it's
> given a unique index, so I've left the check outside the function. This
> seems cleaner anyway: the function stays more focused.
>
>> --- a/src/backend/optimizer/util/plancat.c
>> +++ b/src/backend/optimizer/util/plancat.c
>> @@ -815,7 +815,7 @@ infer_arbiter_indexes(PlannerInfo *root)
>> */
>> if (indexOidFromConstraint == idxForm->indexrelid)
>> {
>> - if (!idxForm->indisunique && onconflict->action ==
>> ONCONFLICT_UPDATE)
>> + if ((!idxForm->indisunique || idxForm->indisexclusion) &&
>> onconflict->action == ONCONFLICT_UPDATE)
>> ereport(ERROR,
>> (errcode(ERRCODE_WRONG_OBJECT_TYPE),
>> errmsg("ON CONFLICT DO UPDATE not supported
>> with exclusion constraints")));
>>
>> Shouldn't this use only idxForm->indisexclusion anyway? Like
>>
>> + if (idxForm->indisexclusion && onconflict->action ==
>> ONCONFLICT_UPDATE)
>>
>> That matches what the error message is reporting afterwards.
>
> Agreed.
>
>> * constraints), so index under consideration can be immediately
>> * skipped if it's not unique
>> */
>> - if (!idxForm->indisunique)
>> + if (!idxForm->indisunique || idxForm->indisexclusion)
>> goto next;
>>
>> Maybe here we need a comment. Or make that a separate statement, like
>
> Yes, that is nice. Done.
>
> Yours,
>