github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-24 23:46:30 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

pq: Cache lookup fail #1595

New Issue
Closed
opened 2025-11-02 04:06:05 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 04:06:05 -06:00
Owner
Copy Link

Originally created by @oliviergareau on GitHub (Mar 5, 2018).

  • Gitea version (or commit ref): 1.3.3
  • Git version: 2.11.0
  • Operating system: Armbian
  • 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:
    2018/03/05 19:04:33 [I] Log Mode: File(Info)
    2018/03/05 19:04:33 [I] XORM Log Mode: File(Info)
    2018/03/05 19:04:33 [I] Cache Service Enabled
    2018/03/05 19:04:33 [I] Session Service Enabled
    2018/03/05 19:04:33 [I] Mail Service Enabled
    2018/03/05 19:04:33 [I] Register Mail Service Enabled
    2018/03/05 19:04:33 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: sync: pq: cache lookup failed for function 669

Description

After a server reboot on version 1.3.3, gitea fails to start with the following error:
[...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: sync: pq: cache lookup failed for function 669 . Google search did not return much about this error and gogs or gitea.

Originally created by @oliviergareau on GitHub (Mar 5, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.3.3 - Git version: 2.11.0 - Operating system: Armbian - 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 - Log gist: 2018/03/05 19:04:33 [I] Log Mode: File(Info) 2018/03/05 19:04:33 [I] XORM Log Mode: File(Info) 2018/03/05 19:04:33 [I] Cache Service Enabled 2018/03/05 19:04:33 [I] Session Service Enabled 2018/03/05 19:04:33 [I] Mail Service Enabled 2018/03/05 19:04:33 [I] Register Mail Service Enabled 2018/03/05 19:04:33 [...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: sync: pq: cache lookup failed for function 669 ## Description After a server reboot on version 1.3.3, gitea fails to start with the following error: `[...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: migrate: sync: pq: cache lookup failed for function 669` . Google search did not return much about this error and gogs or gitea.
GiteaMirror added the issue/not-a-bug label 2025-11-02 04:06:05 -06:00
GiteaMirror commented 2025-11-02 04:06:06 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 7, 2018):

@WhiteRayne2 that means you ever manually deleted a function on your table pg_proc. It should be not related with Gitea.

@lunny commented on GitHub (Mar 7, 2018): @WhiteRayne2 that means you ever manually deleted a function on your table `pg_proc`. It should be not related with Gitea.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/not-a-bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1595
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?