github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 11:37:49 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2216] pq: schema \"paradedb\" does not exist" #6598

New Issue
Closed
opened 2026-04-20 17:11:47 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-20 17:11:47 -05:00
Owner
Copy Link

Originally created by @rhclayto on GitHub (Feb 9, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2216

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

I updated to Vikunja v1.1.0, installed the ParadeDB extension according to their instructions, ensured it was enabled in PostgreSQL, removed the TypeSense section of the config (it was only typesense.enabled: false), & restarted Vikunja. Afterwards, all my tasks & projects were missing from the UI (still there in the database), though labels are still there, & I began receiving the following error messages:

Feb 09 15:47:00 apps vikunja[30495]: time=2026-02-09T15:47:00.022-07:00 level=ERROR msg="[Undone Overdue Tasks Reminder] Could not get undone overdue tasks in the next minute: pq: schema \"paradedb\" does not exist"

Looking in the database, there is indeed no paradedb schema.

At boot the logs show:

Feb 09 15:46:54 apps vikunja[30495]: time=2026-02-09T15:46:54.640-07:00 level=INFO msg="Using config file: /opt/vikunja/config.yml"
Feb 09 15:46:54 apps vikunja[30495]: time=2026-02-09T15:46:54.643-07:00 level=INFO msg="Running migrations…"
Feb 09 15:46:54 apps vikunja[30495]: time=2026-02-09T15:46:54.702-07:00 level=INFO msg="Ran all migrations successfully."
Feb 09 15:46:54 apps vikunja[30495]: time=2026-02-09T15:46:54.707-07:00 level=INFO msg="Vikunja version v1.1.0"
Feb 09 15:46:54 apps vikunja[30495]: time=2026-02-09T15:46:54.713-07:00 level=INFO msg="HTTP server listening on 172.16.30.109:6543"

psql shows me:

postgres=# \dx
                                        List of installed extensions
   Name    | Version | Default version |   Schema   |                      Description
-----------+---------+-----------------+------------+-------------------------------------------------------
 pg_search | 0.21.6  | 0.21.6          | paradedb   | pg_search: Full text search for PostgreSQL using BM25
 plpgsql   | 1.0     | 1.0             | pg_catalog | PL/pgSQL procedural language
 vector    | 0.8.1   | 0.8.1           | public     | vector data type and ivfflat and hnsw access methods
(3 rows)

vikunja doctor output:

Vikunja Doctor
==============

System
  ✓ Version: v1.1.0
  ✓ Go: go1.25.7
  ✓ OS: linux/amd64
  ✓ User: root (uid=0)
  ✓ Working directory: /opt/vikunja
  ✓ User namespace: active (0-65535→100000-165535)
      UIDs inside this container are remapped. See directory ownership check for details.

Configuration
  ✓ Config file: /opt/vikunja/config.yml
  ✓ Public URL: https://todo.example.com/
  ✓ JWT secret: configured (auto-generated)

Database (postgres)
  ✓ Connection: OK
  ✓ Server version: PostgreSQL 17.7 (Debian 17.7-3.pgdg12+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit

Files (local)
  ✓ Path: /opt/vikunja/files
  ✓ Directory exists: yes
  ✓ Directory permissions: 0700
  ✓ Directory owner: vikunja:vikunja (uid=1008, gid=1008)
  ✓ Writable: yes
  ✓ Disk space: 13.6 GB available
  ✓ Stored files: 4 files, 3.6 MB total

Redis
  ✓ Connection: OK (172.16.40.105:6378)

Mailer
  ✓ SMTP connection: OK (172.16.30.108:465)

OpenID Connect
  ✓ Provider: Example SSO: OK

The indices added by CreateParadeDBIndexes (c2a132d56d/pkg/db/db.go (L446C6-L446C27)) are present on the tasks & projects tables.

I upgraded from the release immediately prior to v1.0.0 (skipped 1.0.0 in other words).

What to do?

Vikunja Version

v1.1.0

Browser and version

Firefox/Chrome latest

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @rhclayto on GitHub (Feb 9, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2216 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description I updated to Vikunja v1.1.0, installed the ParadeDB extension according to their instructions, ensured it was enabled in PostgreSQL, removed the TypeSense section of the config (it was only `typesense.enabled: false`), & restarted Vikunja. Afterwards, all my tasks & projects were missing from the UI (still there in the database), though labels are still there, & I began receiving the following error messages: ```syslog Feb 09 15:47:00 apps vikunja[30495]: time=2026-02-09T15:47:00.022-07:00 level=ERROR msg="[Undone Overdue Tasks Reminder] Could not get undone overdue tasks in the next minute: pq: schema \"paradedb\" does not exist" ``` Looking in the database, there is indeed no `paradedb` schema. At boot the logs show: ```syslog Feb 09 15:46:54 apps vikunja[30495]: time=2026-02-09T15:46:54.640-07:00 level=INFO msg="Using config file: /opt/vikunja/config.yml" Feb 09 15:46:54 apps vikunja[30495]: time=2026-02-09T15:46:54.643-07:00 level=INFO msg="Running migrations…" Feb 09 15:46:54 apps vikunja[30495]: time=2026-02-09T15:46:54.702-07:00 level=INFO msg="Ran all migrations successfully." Feb 09 15:46:54 apps vikunja[30495]: time=2026-02-09T15:46:54.707-07:00 level=INFO msg="Vikunja version v1.1.0" Feb 09 15:46:54 apps vikunja[30495]: time=2026-02-09T15:46:54.713-07:00 level=INFO msg="HTTP server listening on 172.16.30.109:6543" ``` psql shows me: ```console postgres=# \dx List of installed extensions Name | Version | Default version | Schema | Description -----------+---------+-----------------+------------+------------------------------------------------------- pg_search | 0.21.6 | 0.21.6 | paradedb | pg_search: Full text search for PostgreSQL using BM25 plpgsql | 1.0 | 1.0 | pg_catalog | PL/pgSQL procedural language vector | 0.8.1 | 0.8.1 | public | vector data type and ivfflat and hnsw access methods (3 rows) ``` vikunja doctor output: ```console Vikunja Doctor ============== System ✓ Version: v1.1.0 ✓ Go: go1.25.7 ✓ OS: linux/amd64 ✓ User: root (uid=0) ✓ Working directory: /opt/vikunja ✓ User namespace: active (0-65535→100000-165535) UIDs inside this container are remapped. See directory ownership check for details. Configuration ✓ Config file: /opt/vikunja/config.yml ✓ Public URL: https://todo.example.com/ ✓ JWT secret: configured (auto-generated) Database (postgres) ✓ Connection: OK ✓ Server version: PostgreSQL 17.7 (Debian 17.7-3.pgdg12+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit Files (local) ✓ Path: /opt/vikunja/files ✓ Directory exists: yes ✓ Directory permissions: 0700 ✓ Directory owner: vikunja:vikunja (uid=1008, gid=1008) ✓ Writable: yes ✓ Disk space: 13.6 GB available ✓ Stored files: 4 files, 3.6 MB total Redis ✓ Connection: OK (172.16.40.105:6378) Mailer ✓ SMTP connection: OK (172.16.30.108:465) OpenID Connect ✓ Provider: Example SSO: OK ``` The indices added by `CreateParadeDBIndexes` (https://github.com/go-vikunja/vikunja/blob/c2a132d56de794529c77f952b47c788970f4db7b/pkg/db/db.go#L446C6-L446C27) are present on the tasks & projects tables. I upgraded from the release immediately prior to v1.0.0 (skipped 1.0.0 in other words). What to do? ### Vikunja Version v1.1.0 ### Browser and version Firefox/Chrome latest ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2026-04-20 17:11:48 -05:00
Author
Owner
Copy Link

@rhclayto commented on GitHub (Feb 10, 2026):

Okay, I solved this. I had installed the pg_search extension on a PostgreSQL instance on Debian & enabled it, but you have to first create the paradedb schema on the vikunja database, then enable the pg_search extension on the vikunja database. I didn't find this information on the ParadeDB docs site. I actually found it on the PostGIS Ubuntu installation instructions on their docs site.

Would you like a PR for some docs in Vikunja making this clear to users?

<!-- gh-comment-id:3875364540 --> @rhclayto commented on GitHub (Feb 10, 2026): Okay, I solved this. I had installed the pg_search extension on a PostgreSQL instance on Debian & enabled it, but you have to first create the paradedb schema on the vikunja database, then enable the pg_search extension on the vikunja database. I didn't find this information on the ParadeDB docs site. I actually found it on the PostGIS Ubuntu installation instructions on their docs site. Would you like a PR for some docs in Vikunja making this clear to users?
GiteaMirror commented 2026-04-20 17:11:49 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 11, 2026):

A docs PR would be great!

Here on this page would be good: https://github.com/go-vikunja/website/blob/main/src/content/docs/setup/paradedb.mdoc

<!-- gh-comment-id:3887622847 --> @kolaente commented on GitHub (Feb 11, 2026): A docs PR would be great! Here on this page would be good: https://github.com/go-vikunja/website/blob/main/src/content/docs/setup/paradedb.mdoc
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
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/vikunja#6598
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?