Open
Conversation
Member
|
Thanks for the proposed fix - but this sounds like a duplicate of #177. Although the behavior is ugly it is intentional. |
Author
|
@schmiddy I understand. In this case, extra validation would be helpful to avoid issues and also some mention in the docs. Thank you |
za-arthur
approved these changes
Apr 6, 2023
Collaborator
There was a problem hiding this comment.
Thanks for the PR. It looks good to me.
Thanks for the proposed fix - but this sounds like a duplicate of #177. Although the behavior is ugly it is intentional.
I think that #177 solves the issue in a different way by enforcing quotes. On the other hand this PR changes internal behavior of how table name is retrieved which is used later:
Line 2191 in 999b854
On the other hand it is probably worth to add new tests.
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
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.
Currently, the
--only-indexesoption doesn't escape table names given in the command line and causes the following error:Example:
Note: There's a workaround, you can add double quotes to the table name, however, this is something very easy to miss and cause the database become in an invalid state with a lot of indexes uncomplete rebuilt.
This PR change the SQL query used in
bin/pg_repackand fix the issue.