Which table does gitea store its users when using postgres? #2023

New Issue

GiteaMirror · 2025-11-02T04:21:30-06:00

GiteaMirror commented

2025-11-02 04:21:30 -06:00

Originally created by @savyajha on GitHub (Jul 7, 2018).

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

Description

I'd like to know which table gitea stores its users in. I've been trying to migrate from mysql to postgres, but for the life of me I don't understand where gitea stores its users. To check where it stores users, I launched two different instances of gitea, with one using mysql and the other using postgresql. I then added a user during installation for both. I checked the user table in both mysql and postgres. The mysql one is populated as I expect it to, but I don't see the postgres user table being populated when I add a new user.

This is quite vexing, because my production instance has all its users in the user table in mysql which I cannot migrate over: I don't know where users get stored in postgres. Every other table is migrating over perfectly fine.

Originally created by @savyajha on GitHub (Jul 7, 2018).  - Gitea version (or commit ref): 1.4.3 - Git version: 2.18.0 - Operating system: Arch Linux - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant ## Description I'd like to know which table gitea stores its users in. I've been trying to migrate from mysql to postgres, but for the life of me I don't understand where gitea stores its users. To check where it stores users, I launched two different instances of gitea, with one using mysql and the other using postgresql. I then added a user during installation for both. I checked the `user` table in both mysql and postgres. The mysql one is populated as I expect it to, but I don't see the postgres `user` table being populated when I add a new user. This is quite vexing, because my production instance has all its users in the `user` table in mysql which I cannot migrate over: I don't know where users get stored in postgres. Every other table is migrating over perfectly fine.

GiteaMirror added the type/question label 2025-11-02 04:21:30 -06:00

GiteaMirror closed this issue

2025-11-02 04:21:30 -06:00

GiteaMirror commented

2025-11-02 04:21:31 -06:00

@gsantner commented on GitHub (Jul 7, 2018):

maybe do a fresh install and and just purge db after install (e.g. in VM/docker)? this probably will answer all other questions like "where is X stored"

@gsantner commented on GitHub (Jul 7, 2018): maybe do a fresh install and and just purge db after install (e.g. in VM/docker)? this probably will answer all other questions like "where is X stored"

GiteaMirror commented

2025-11-02 04:21:31 -06:00

@savyajha commented on GitHub (Jul 7, 2018):

I found it, sorry, I overlooked something silly. Now the only problem is that it tells me my password is wrong. :/

@savyajha commented on GitHub (Jul 7, 2018): I found it, sorry, I overlooked something silly. Now the only problem is that it tells me my password is wrong. :/

GiteaMirror commented

2025-11-02 04:21:32 -06:00

@techknowlogick commented on GitHub (Jul 7, 2018):

@savyajha you can reset password via command line: https://docs.gitea.io/en-us/command-line/

I'm going to close this ticket now as you've discovered the table.

@techknowlogick commented on GitHub (Jul 7, 2018): @savyajha you can reset password via command line: https://docs.gitea.io/en-us/command-line/ I'm going to close this ticket now as you've discovered the table.

GiteaMirror commented

2025-11-02 04:21:32 -06:00

@Freccia commented on GitHub (Jul 8, 2018):

Hello,
I had the same issue (user table seems unpopulated), which is more postgres related, but I solved by doing this:

$ sudo -u postgres psql
postgres=#  \c gitea
gitea=# SELECT * FROM public.user;

@Freccia commented on GitHub (Jul 8, 2018): Hello, I had the same issue (`user` table seems unpopulated), which is more `postgres` related, but I solved by doing this: ``` $ sudo -u postgres psql postgres=# \c gitea gitea=# SELECT * FROM public.user; ```

GiteaMirror commented

2025-11-02 04:21:32 -06:00

@savyajha commented on GitHub (Jul 8, 2018):

Yeah, thanks. Another way is to quote "user". My problem is that the tool I used for import from mysql didn't associate the tables with the public schema, which meant that gitea couldn't really access them.

@savyajha commented on GitHub (Jul 8, 2018): Yeah, thanks. Another way is to quote `"user"`. My problem is that the tool I used for import from mysql didn't associate the tables with the public schema, which meant that gitea couldn't really access them.

GiteaMirror referenced this issue

2025-11-02 12:04:12 -06:00

[PR #2023] [MERGED] Fix displaying commits and files of PR created from now deleted fork #16184

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2023