Remove Postgres NOTICE spew generated by DROP FUNCTION IF EXISTS
#7911
Conversation
This file contains 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
Use an explicit conditional when using `DropFunction` in various places of bootstrap and for reflection cache functions. This makes it actually possible to NOTICE postgres messages in bootstrap (pun intended). Equipped with this new visibility fix the name of the indexes we place on properties.
msullivan
approved these changes
Oct 23, 2024
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.
Use an explicit conditional when using
DropFunctionin various placesof bootstrap and for reflection cache functions. This makes it actually
possible to NOTICE postgres messages in bootstrap (pun intended). Equipped
with this new visibility fix the name of the indexes we place on
properties.