Gitea cannot be installed on posgresql schema different to public #3624

New Issue

GiteaMirror · 2025-11-02T05:19:56-06:00

GiteaMirror commented

2025-11-02 05:19:56 -06:00

Originally created by @Rizzen59 on GitHub (Jul 19, 2019).

Gitea version (or commit ref): 1.8.3 and 1.9.0-rc2
Git version: 2.22.0
Operating system: CentOS 7
Database (use [x]):
- PostgreSQL (11)
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- Not relevant
- No
Log gist:

Description

If default schema for user is different of public (the best way), schema is created on gitea on the user default schema.
On boot, the check for existing column id on table version is executed on schema public , then gitea try to add column but column already exist on user's default schema and crash.

Log :
SELECT column_name FROM INFORMATION_SCHEMA.COLUMNS WHERE table_schema = $1 AND table_name = $2 AND column_name = $3 [public version id]

Originally created by @Rizzen59 on GitHub (Jul 19, 2019).   - Gitea version (or commit ref): 1.8.3 and 1.9.0-rc2 - Git version: 2.22.0 - Operating system: CentOS 7 - Database (use `[x]`): - [x] PostgreSQL (11) - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] Not relevant - [ ] No - Log gist: ## Description If default schema for user is different of public (the best way), schema is created on gitea on the user default schema. On boot, the check for existing column id on table version is executed on schema public , then gitea try to add column but column already exist on user's default schema and crash. Log : SELECT column_name FROM INFORMATION_SCHEMA.COLUMNS WHERE table_schema = $1 AND table_name = $2 AND column_name = $3 [**public** version id]

GiteaMirror added the issue/duplicate label 2025-11-02 05:19:56 -06:00

GiteaMirror closed this issue

2025-11-02 05:19:56 -06:00

GiteaMirror commented

2025-11-02 05:19:57 -06:00

@lafriks commented on GitHub (Jul 19, 2019):

I think there was issue for this already, there was even draft PR to fix this but it never got finished

@lafriks commented on GitHub (Jul 19, 2019): I think there was issue for this already, there was even draft PR to fix this but it never got finished

GiteaMirror commented

2025-11-02 05:19:57 -06:00

@lunny commented on GitHub (Jul 20, 2019):

duplicated with #5152