Prevent Sync failure with non-regular indexes on Postgres #2174

Merged
lunny merged 1 commits from zeripath/xorm:fix-postgres-sync-failure-with-non-regular-index into master 4 weeks ago
Collaborator

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

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>
zeripath added 1 commit 4 weeks ago
continuous-integration/drone/pr Build is passing Details
af675201d3
Prevent Sync failure with non-regular indexes on Postgres
lunny approved these changes 4 weeks ago
lunny merged commit c900ecc87f into master 4 weeks ago
zeripath deleted branch fix-postgres-sync-failure-with-non-regular-index 4 weeks ago
Poster
Collaborator

@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 ?

@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 ?
Owner

@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.

> @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.
lunny added this to the 1.3.2 milestone 4 weeks ago

Reviewers

lunny approved these changes 4 weeks ago
continuous-integration/drone/pr Build is passing
The pull request has been merged as c900ecc87f.
Sign in to join this conversation.
Loading…
There is no content yet.