Updates for Learned Indexes, NULLs are equal in DISTINCT but unequal in UNIQUE, fsyncgate & SERIAL is non-transactional. #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added explanations in the commit messages, but most are self explanatory if you click through.
If it's not clear:
Learned Indexes appear to be a theoretical index, that hasn't been implemented in PostgreSQL, but is an interesting topic about the application of ML on datasets. The link provides many references.
The NULL one is pretty self explanatory, the link provides a table of how NULL is treated differently in different contexts.
fsyncgate points in a wikipedia page that outlines the whole history of fsyncgate.
SERIAL is technically non-transactional because when you rollback a transaction, SERIAL is still incremented outside of the transaction.