Skip to content

After 1.1.0 upgrade: relation "IDX_repo_unit_S" already exists #1261

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
2 of 7 tasks
rain0r opened this issue Mar 15, 2017 · 4 comments
Closed
2 of 7 tasks

After 1.1.0 upgrade: relation "IDX_repo_unit_S" already exists #1261

rain0r opened this issue Mar 15, 2017 · 4 comments
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@rain0r
Copy link

rain0r commented Mar 15, 2017

  • Gitea version (or commit ref): 1.1.0
  • Git version: 2.12.0
  • Operating system: Gentoo Linux
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

After upgrading to 1.1.0 via Gentoo portage I can't start gitea because of:

2017/03/15 12:27:52 [...itea/routers/init.go:54 GlobalInit()] [E] Failed to initialize ORM engine: migrate: do migrate: CreateIndexes RepoUnit: pq: relation "IDX_repo_unit_S" already exists ...
@lunny lunny added the type/question Issue needs no code to be fixed, only a description on how to fix it yourself. label Mar 15, 2017
@lunny
Copy link
Member

lunny commented Mar 15, 2017

Please drop the table repo_unit manually and start again.

@Funzinator Funzinator mentioned this issue Mar 15, 2017
Closed
7 tasks
@rain0r
Copy link
Author

rain0r commented Mar 22, 2017

That worked.

@rain0r rain0r closed this as completed Mar 22, 2017
@strk
Copy link
Member

strk commented Mar 22, 2017

@lunny any way to make our migrations immune from this issue ? (might help when people try to migrate from a newer Gogs, for example)

@cez81 cez81 mentioned this issue Mar 22, 2017
Closed
7 tasks
@lunny
Copy link
Member

lunny commented Mar 23, 2017

It's hard to resolve this problem. Many operations cannot be reverted.

@go-gitea go-gitea locked and limited conversation to collaborators Nov 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lunny @strk @rain0r