Page 1 of 1

PostgreSQL jQuery error in the PostgreSQL logs

Published: October 3, 2025 - 8:11 AM
by Mikael S
Good morning,

In the database logs, I came across this

Code: Select all

2025-10-02 23:59:27.817 CEST [1202] LOG:  starting PostgreSQL 15.14 (Debian 15.14-0+deb12u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit
2025-10-02 23:59:27.822 CEST [1202] LOG:  listening on IPv6 address "::1", port 5432
2025-10-02 23:59:27.822 CEST [1202] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2025-10-02 23:59:27.824 CEST [1202] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-10-02 23:59:27.856 CEST [1224] LOG:  database system was shut down at 2025-10-02 23:59:02 CEST
2025-10-02 23:59:27.888 CEST [1202] LOG:  database system is ready to accept connections
2025-10-02 23:59:30.866 CEST [1794] wapt@wapt ERROR:  extension "jsquery" is not available
2025-10-02 23:59:30.866 CEST [1794] wapt@wapt DETAIL:  Could not open extension control file "/usr/share/postgresql/15/extension/jsquery.control": No such file or directory.
2025-10-02 23:59:30.866 CEST [1794] wapt@wapt HINT:  The extension must first be installed on the system where PostgreSQL is running.
2025-10-02 23:59:30.866 CEST [1794] wapt@wapt STATEMENT:  CREATE EXTENSION if not exists jsquery;
2025-10-02 23:59:30.867 CEST [1794] wapt@wapt WARNING:  there is no transaction in progress
2025-10-03 00:02:58.370 CEST [2675] postgres@wapt LOG:  could not send data to client: Broken pipe
2025-10-03 00:02:58.370 CEST [2675] postgres@wapt STATEMENT:  COPY public.hostauditdata (id, host_id, value_id, value_date, value_section, value_key, value, expiration_date, created_on, created_by) TO stdout;
2025-10-03 00:02:58.370 CEST [2675] postgres@wapt ERROR:  canceling statement due to user request
2025-10-03 00:02:58.370 CEST [2675] postgres@wapt STATEMENT:  COPY public.hostauditdata (id, host_id, value_id, value_date, value_section, value_key, value, expiration_date, created_on, created_by) TO stdout;
2025-10-03 00:02:58.370 CEST [2675] postgres@wapt FATAL:  connection to client lost
You don't mention the need to install the postgresql-15-jsquery package under bookworm in the wiki. Or perhaps it's on a different page than https://www.wapt.fr/en/doc/wapt-server- ... er-install



Sincerely,

Re: PostgreSQL jQuery error in the Postgres logs

Published: October 3, 2025 - 11:04 AM
by dcardon
Hi Mickael,

the jQuery extension is no longer necessary for WAPT itself. And on a fresh install, the postconf script only installs it if it's available on the system. But it's true that it can cause problems on a backup restore or server reinstall. This extension can be used in SQL/JSON queries.

I'll check with the team to see if we can add it back to the documentation during installation or if we can find a better way to clean this up during an upgrade.

Regards,

Denis