Row opt-in #7
Merged
Row opt-in #7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
While STATEMENT-level triggers are better for bulk operations, being vastly more performant when INSERTing or DELETEing large swaths of data, ROW-level triggers can be more performant on individual UPDATE operations, since they can opt _not_ to update the haystack if none of the indexed fields are actually updated. This update gives the option to use one or the other depending on application concerns (though it still defaults to STATEMENT as before).
theghall
approved these changes
Jan 13, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
While STATEMENT-level triggers are better for bulk operations, being vastly more performant when INSERTing or DELETEing large swaths of data, ROW-level triggers can be more performant on individual UPDATE operations, since they can opt not to update the haystack if none of the indexed fields are actually updated. This update gives the option to use one or the other depending on application concerns (though it still defaults to STATEMENT as before).