If you already self-manage Postgres, you may prefer to install ParadeDB directly within your self-managed Postgres instead of deploying the ParadeDB Helm chart.
This can be done by installing the pg_search
extension, which powers all of ParadeDB’s full text search and analytics:
Ensure that you have superuser access to the Postgres database.
Next, install libicu
.
ParadeDB provides prebuilt binaries for our extension on
Postgres 14, 15, 16, and 17 are available. If you are using a different version of Postgres or a different operating system, you will need to build the extension from source.
The prebuilt releases can be found in GitHub Releases.
You can replace 0.16.0
with the pg_search
version you wish to install and
17
with the version of Postgres you are using.
If you are a ParadeDB Enterprise user, you should have received a copy of the enterprise binaries. Please contact sales for access.
postgresql.conf
Next, add the extension(s) to shared_preload_libraries
in postgresql.conf
. Adding pg_search
to shared_preload_libraries
is unnecessary if your Postgres version is 17 or higher.
Reload the Postgres server for these changes to take effect.
Finally, connect to your Postgres database via your client of choice (e.g. psql
) and run the following command:
pg_search
can be combined with pgvector
for hybrid search. You can find
the instructions for installing pgvector
here.