mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-11-03 20:17:59 +00:00
e27b43c482
* migrates nav data format and updates docs pages * removes sidebar_title from content files
141 lines
4.7 KiB
Plaintext
141 lines
4.7 KiB
Plaintext
---
|
||
layout: docs
|
||
page_title: PostgreSQL - Storage Backends - Configuration
|
||
description: |-
|
||
The PostgreSQL storage backend is used to persist Vault's data in a PostgreSQL
|
||
server or cluster.
|
||
---
|
||
|
||
# PostgreSQL Storage Backend
|
||
|
||
The PostgreSQL storage backend is used to persist Vault's data in a
|
||
[PostgreSQL][postgresql] server or cluster.
|
||
|
||
- **High Availability** – the PostgreSQL storage backend supports
|
||
high availability. Requires PostgreSQL 9.5 or later.
|
||
|
||
- **Community Supported** – the PostgreSQL storage backend is supported by the
|
||
community. While it has undergone review by HashiCorp employees, they may not
|
||
be as knowledgeable about the technology. If you encounter problems with them,
|
||
you may be referred to the original author.
|
||
|
||
```hcl
|
||
storage "postgresql" {
|
||
connection_url = "postgres://user123:secret123!@localhost:5432/vault"
|
||
}
|
||
```
|
||
|
||
~> **Note:** The PostgreSQL storage backend plugin will attempt to use SSL
|
||
when connecting to the database. If SSL is not enabled the `connection_url`
|
||
will need to be configured to disable SSL. See the documentation below
|
||
to disable SSL.
|
||
|
||
The PostgreSQL storage backend does not automatically create the table. Here is
|
||
some sample SQL to create the schema and indexes.
|
||
|
||
```sql
|
||
CREATE TABLE vault_kv_store (
|
||
parent_path TEXT COLLATE "C" NOT NULL,
|
||
path TEXT COLLATE "C",
|
||
key TEXT COLLATE "C",
|
||
value BYTEA,
|
||
CONSTRAINT pkey PRIMARY KEY (path, key)
|
||
);
|
||
|
||
CREATE INDEX parent_path_idx ON vault_kv_store (parent_path);
|
||
```
|
||
|
||
Store for HAEnabled backend
|
||
|
||
```sql
|
||
CREATE TABLE vault_ha_locks (
|
||
ha_key TEXT COLLATE "C" NOT NULL,
|
||
ha_identity TEXT COLLATE "C" NOT NULL,
|
||
ha_value TEXT COLLATE "C",
|
||
valid_until TIMESTAMP WITH TIME ZONE NOT NULL,
|
||
CONSTRAINT ha_key PRIMARY KEY (ha_key)
|
||
);
|
||
```
|
||
|
||
If you're using a version of PostgreSQL prior to 9.5, create the following function:
|
||
|
||
```sql
|
||
CREATE FUNCTION vault_kv_put(_parent_path TEXT, _path TEXT, _key TEXT, _value BYTEA) RETURNS VOID AS
|
||
$$
|
||
BEGIN
|
||
LOOP
|
||
-- first try to update the key
|
||
UPDATE vault_kv_store
|
||
SET (parent_path, path, key, value) = (_parent_path, _path, _key, _value)
|
||
WHERE _path = path AND key = _key;
|
||
IF found THEN
|
||
RETURN;
|
||
END IF;
|
||
-- not there, so try to insert the key
|
||
-- if someone else inserts the same key concurrently,
|
||
-- we could get a unique-key failure
|
||
BEGIN
|
||
INSERT INTO vault_kv_store (parent_path, path, key, value)
|
||
VALUES (_parent_path, _path, _key, _value);
|
||
RETURN;
|
||
EXCEPTION WHEN unique_violation THEN
|
||
-- Do nothing, and loop to try the UPDATE again.
|
||
END;
|
||
END LOOP;
|
||
END;
|
||
$$
|
||
LANGUAGE plpgsql;
|
||
```
|
||
|
||
## `postgresql` Parameters
|
||
|
||
- `connection_url` `(string: <required>)` – Specifies the connection string to
|
||
use to authenticate and connect to PostgreSQL. The connection URL can also be
|
||
set using the `VAULT_PG_CONNECTION_URL` environment variable. A full list of supported
|
||
parameters can be found in [the pq library documentation][pglib]. For example
|
||
connection string URLs, see the examples section below.
|
||
|
||
- `table` `(string: "vault_kv_store")` – Specifies the name of the table in
|
||
which to write Vault data. This table must already exist (Vault will not
|
||
attempt to create it).
|
||
|
||
- `max_idle_connections` `(int)` - Default not set. Sets the maximum number of
|
||
connections in the idle connection pool. See
|
||
[golang docs on SetMaxIdleConns][golang_setmaxidleconns] for more information.
|
||
Requires 1.2 or later.
|
||
|
||
- `max_parallel` `(string: "128")` – Specifies the maximum number of concurrent
|
||
requests to PostgreSQL.
|
||
|
||
- `ha_enabled` `(string: "true|false")` – Default not enabled, requires 9.5 or later.
|
||
|
||
- `ha_table` `(string: "vault_ha_locks")` – Specifies the name of the table to use
|
||
for storing high availability information. This table must already exist (Vault
|
||
will not attempt to create it).
|
||
|
||
## `postgresql` Examples
|
||
|
||
### Custom SSL Verification
|
||
|
||
This example shows connecting to a PostgreSQL cluster using full SSL
|
||
verification (recommended).
|
||
|
||
```hcl
|
||
storage "postgresql" {
|
||
connection_url = "postgres://user:pass@localhost:5432/database?sslmode=verify-full"
|
||
}
|
||
```
|
||
|
||
To disable SSL verification (not recommended), replace `verify-full` with
|
||
`disable`:
|
||
|
||
```hcl
|
||
storage "postgresql" {
|
||
connection_url = "postgres://user:pass@localhost:5432/database?sslmode=disable"
|
||
}
|
||
```
|
||
|
||
[golang_setmaxidleconns]: https://golang.org/pkg/database/sql/#DB.SetMaxIdleConns
|
||
[postgresql]: https://www.postgresql.org/
|
||
[pglib]: https://godoc.org/github.com/lib/pq#hdr-Connection_String_Parameters
|