When building a system image, we start from a community postgres image.
There is the chance that newer postgres packages are released, and they
could be upgraded when installing the supported extensions. We want to
prevent this scenario, as it could lead to unexpected versions in the
container image.
Closes#186
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
build-essential and python3-dev are required to build LZ4 on arm64 since there aren't pre-compiled wheel available for this architecture.
Also, switch back to using the latest qemu image.
Signed-off-by: Niccolò Fei <niccolo.fei@enterprisedb.com>
A couple of things were fixed in Barman that allow us to remove
build-essentials and a bunch of development packages that were
only needed during the build process.
Closes#117
Signed-off-by: Jonathan Gonzalez V <jonathan.gonzalez@enterprisedb.com>
AI is a hot topic in Cloud Native environments (not only there).
Providing a way to easily add `pgvector` to CloudNativePG deployments
can potentially increase the adoption of Postgres in these contexts.
It is an extension that can be fully controlled by a standard Postgres
user, like the application user in CloudNativePG, without requiring
any settings in shared_preload_libraries.
License-wise that extension creates no problems.
Closes#70
Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
