pgvector In Every New PostgreSQL Database

pgvector from AppStream for PostgreSQL 16, created in template1 so every new database starts with it, and in the databases you list. The live test creates a database, finds the extension there, gets the nearest neighbour from an HNSW index the planner uses, and sees a database made from template0 lack the type. Original role, live-tested on Rocky Linux 10.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

ansibleMulti-cloud & platform-agnosticDatabasesv1.0.0live-tested

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

ClickHouse, An Analytics Database Proven By A MergeTree Round Trip Dragonfly, A Redis-Compatible Store Proven Over RESP InfluxDB 3 Core, Proven By A Write And An SQL Query MariaDB That Ran Its Own Secure Installation Meilisearch, A Search Engine Proven By An Indexed Search OpenSearch, One Node Proven By An Index And A Search PgBouncer With SCRAM, Proven Against PostgreSQL 16 PocketBase On Loopback, A Collection Round-Tripped

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_pgvector" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-pgvector/any"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.