Avoid PG exception handling - unique constraint #27
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
The design of tsk_host_addresses table accounts for unique constraints on tsk_host_addresses_address_type_address_key Insert attempts to this table does not need to trigger an exception processing flow in the pg db layer. It can be ignored safely. Adding ON CONFLICT DO NOTHING pattern for improved performance.
APriestman
approved these changes
Dec 9, 2025
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.
The design of tsk_host_addresses table accounts for unique constraints on tsk_host_addresses_address_type_address_key
Insert attempts to this table does not need to trigger an exception processing flow in the pg db layer. It can be ignored safely. Adding ON CONFLICT DO NOTHING pattern for improved performance.