pg_search
. Upgrading ParadeDB is as simple as updating the pg_search
extension.
pgvector
for vector search. This extension is not managed by
ParadeDB. Please refer to the pgvector
documentation
for instructions on how to upgrade it.paradedb.version_info()
:
paradedb.version_info()
is the actual version of pg_search
that is installed,
whereas pg_extension
is what Postgres’ catalog thinks the version of the extension is.
If paradedb.version_info()
is greater than pg_extension
, it typically means that ALTER EXTENSION
was not run after the previous upgrade, and that the SQL upgrade scripts were not applied.
If pg_extension
is greater than paradedb.version_info()
, it means that the extension didn’t fully upgrade, and that Postgres needs to be restarted.
pg_search
is 0.17.2
. Please refer to the releases page for all available versions of pg_search
.
paradedb
chart to the latest version.paradedb
chart.version.paradedb
in the chart README.
helm upgrade
with the latest version of the chart and the latest version of the extension.
<helm_version>
with the latest version of the chart and <paradedb_version>
with the latest version of the extension.
docker stop paradedb
.
latest
to pull the latest Docker image. You can find the full list of available tags on Docker Hub.
0.17.2
.
docker run paradedb
.pg_ctl stop -D </path/to/data/directory>
).pg_ctl start -D </path/to/data/directory>
).pg_search
is installed in. This step is required regardless of the environment that ParadeDB is installed in (Helm, Docker, or self-managed Postgres).