Skip to content

The DUMP command does not create any SEQUENCE objects when using postgresql #5472

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.

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

Closed
2 of 7 tasks
oicq1699 opened this issue Dec 5, 2018 · 4 comments
Closed
2 of 7 tasks
Labels
issue/duplicate The issue has already been reported. type/bug

Comments

@oicq1699
Copy link

oicq1699 commented Dec 5, 2018

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • 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

I use postgresql 11, Gitea version 1.6.0, I use the dump command to generate a backup file, When I perform the restore operation, the system reports table_id_seq does not exist error. I checked the gitea-db.sql file and found that there are no statements for creating all SEQUENCE objects. I tried to export with the pg_dump command that comes with postgresql, everything works fine. I think this should be a bug.

Screenshots

@lunny lunny added the type/bug label Dec 5, 2018
@ghost
Copy link

ghost commented Dec 24, 2018

This looks to be the same as #4407

@oicq1699
Copy link
Author

This looks to be the same as #4407

Yes, the same problem, but it has not been solved. I also use the methods you provide to recover the database.

@lafriks lafriks added the issue/duplicate The issue has already been reported. label Jan 8, 2019
@lafriks
Copy link
Member

lafriks commented Jan 8, 2019

Closing as duplicate of #4407

@lafriks lafriks closed this as completed Jan 8, 2019
@belminf
Copy link

belminf commented Mar 3, 2019

@oicq1699 FYI, had similar issue. Posted how I fixed it at #4407 .

@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported. type/bug
Projects
None yet
Development

No branches or pull requests

4 participants