CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
9a9efd16e2c1def456a69efc3ddcb5b4bcec2f4e
threshold/website/content/docs/installing/postgres.mdx
T

19 lines
621 B
Plaintext
Raw Normal View History

docs: break out the configuration complete examples into the main config overview (#546)
2020-10-06 07:40:29 -07:00
---
layout: docs
docs: few typos and tidy ups (#561)
2020-10-07 08:24:12 +08:00
page_title: Postgres Installation
docs: break out the configuration complete examples into the main config overview (#546)
2020-10-06 07:40:29 -07:00
sidebar_title: Postgres Install
description: |-
docs: few typos and tidy ups (#561)
2020-10-07 08:24:12 +08:00
Postgres configuration for Boundary
docs: break out the configuration complete examples into the main config overview (#546)
2020-10-06 07:40:29 -07:00
---
# Postgres Configuration
This section covers Postgres-specific installation requirements.
## Version
Minor doc wording fixups (#581)
2020-10-08 14:24:15 -04:00
Boundary has only been tested on Postgres 11 or greater.
docs: break out the configuration complete examples into the main config overview (#546)
2020-10-06 07:40:29 -07:00
docs: few typos and tidy ups (#561)
2020-10-07 08:24:12 +08:00
## Network
docs: break out the configuration complete examples into the main config overview (#546)
2020-10-06 07:40:29 -07:00
Minor doc wording fixups (#581)
2020-10-08 14:24:15 -04:00
Boundary controllers must be able to reach Postgres. In non-HA configurations, this means Boundary servers; if you're running in [high availability](/docs/installing/high-availability), then the controllers need access to the Postgres server infrastructure. Worker nodes never need access to the database.
Reference in new issue Copy Permalink