LobeHub #1783

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using, or where do you have Problems?

Lobehub

📝 Provide a clear and concise description of the issue.

The LobeHub install script fails during PostgreSQL extension creation. The pg_search extension (from ParadeDB) requires being loaded via shared_preload_libraries in postgresql.conf before CREATE EXTENSION pg_search can succeed. The current install script installs the ParadeDB .deb package and immediately calls setup_postgresql_db with PG_DB_EXTENSIONS="vector,pg_search" without configuring shared_preload_libraries, causing a hard failure.

This is a regression introduced by a recent ParadeDB release. Earlier testers (issue #1625, comments dated April 14) reported successful installs, but the latest ParadeDB build (fetched dynamically via api.github.com/repos/paradedb/paradedb/releases/latest) now enforces the preload requirement.

Suggested fix in install/lobehub-install.sh, between the ParadeDB .deb install and setup_postgresql_db:

PG_CONF="/etc/postgresql/17/main/postgresql.conf"
if ! grep -q "shared_preload_libraries.*pg_search" "$PG_CONF"; then
  echo "shared_preload_libraries = 'pg_search'" >> "$PG_CONF"
fi
systemctl restart postgresql

🔄 Steps to reproduce the issue.

1. On a Proxmox VE 9.1.9 host (kernel 7.0.0-3-pve), run the LobeHub helper script:

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/lobehub.sh)"

2. Accept default settings (Debian 13 LXC, unprivileged, 6 cores, 10240 MiB RAM, 15 GB disk).
3. Wait until the script reaches the step Setting up PostgreSQL Database.
4. Installation aborts with exit code 1 immediately after CREATE EXTENSION for pg_search.

❌ Paste the full error output (if available).

Get:1 https://apt.postgresql.org/pub/repos/apt trixie-pgdg/main amd64 postgresql-17-pgvector amd64 0.8.2-1.pgdg13+1 [263 kB]
Fetched 263 kB in 0s (1409 kB/s)
Selecting previously unselected package postgresql-17-pgvector.
(Reading database ... 30857 files and directories currently installed.)
Preparing to unpack .../postgresql-17-pgvector_0.8.2-1.pgdg13+1_amd64.deb ...
Unpacking postgresql-17-pgvector (0.8.2-1.pgdg13+1) ...
Setting up postgresql-17-pgvector (0.8.2-1.pgdg13+1) ...
Processing triggers for postgresql-common (290.pgdg13+1) ...
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
Removing obsolete dictionary files:
[2026-05-04 15:04:27] [INFO] Installing pg_search from ParadeDB
[2026-05-04 15:04:32] [OK] Installed pg_search from ParadeDB
[2026-05-04 15:04:32] [INFO] Setting up PostgreSQL Database
CREATE ROLE
CREATE DATABASE
CREATE EXTENSION
ERROR: pg_search must be loaded via shared_preload_libraries. Add 'pg_search' to shared_preload_libraries in postgresql.conf and restart Postgres.
[2026-05-04 15:04:33] [ERROR] in line 7171: exit code 1 (General error / Operation not permitted)
[2026-05-04 15:04:33] sudo -u postgres psql -d lobehub -c CREATE EXTENSION IF NOT EXISTS pg_search;

📋 Full log: /root/.install-5f316076.log

✖️ Installation failed in container 141 (exit code: 1)

🖼️ Additional context (optional).

• Proxmox VE: 9.1.9
• Host kernel: 7.0.0-3-pve
• LXC: Debian 13 (trixie), unprivileged, default helper-script settings (6 vCPU, 10 GB RAM, 15 GB disk)
• PostgreSQL: 17 (apt.postgresql.org trixie-pgdg)
• pgvector: 0.8.2-1.pgdg13+1
• pg_search: latest ParadeDB release fetched dynamically by the script at install time
• Reproduced consistently on a fresh container.
• Related: issue LobeHub #1625 (LobeHub tracking issue, "Ready For Testing"). Earlier successful tests (comments dated April 14, 2026) predate the ParadeDB release that enforces shared_preload_libraries.
• The first CREATE EXTENSION line that succeeds corresponds to vector; the failure is on pg_search only.