Prevent Sync failure with non-regular indexes on Postgres #2174
No reviewers
Labels
No Label
backport/done
backport/v1
blocked
db
oracle
db
sqlserver
duplicate
feature
cache
frontport/done
frontport/main
invalid
kind
breaking
kind
bug
kind
build
kind
dependencies
kind
docs
kind
driver
kind
enhancement
kind
feature
kind
performance
kind
proposal
kind
question
kind
refactor
kind
testing
need
feedback
need
test
proposal:accepted
RaspBerry Pi
regression
skip-changelog
upstream
wip
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: xorm/xorm#2174
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "zeripath/xorm:fix-postgres-sync-failure-with-non-regular-index"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When dropping indexes in Postgres if the index is non-regular we
should not attempt to regularise the index name as it is already correct.
Signed-off-by: Andrew Thornton art27@cantab.net
@lunny have there been significant changes in xorm since we released 1.17 of gitea or can we just take the current head and backport to Gitea 1.17 ?
Just minor changes, so I think it can be backport to Gitea v1.17. Let me have a tag at first.