|
30 | 30 | databases:
|
31 | 31 | foo: zalando
|
32 | 32 | postgresql:
|
33 |
| - version: "15" |
| 33 | + version: "16" |
34 | 34 | ```
|
35 | 35 |
|
36 | 36 | Once you cloned the Postgres Operator [repository](https://github.com/zalando/postgres-operator)
|
@@ -109,7 +109,7 @@ metadata:
|
109 | 109 | spec:
|
110 | 110 | [...]
|
111 | 111 | postgresql:
|
112 |
| - version: "15" |
| 112 | + version: "16" |
113 | 113 | parameters:
|
114 | 114 | password_encryption: scram-sha-256
|
115 | 115 | ```
|
@@ -517,7 +517,7 @@ Postgres Operator will create the following NOLOGIN roles:
|
517 | 517 |
|
518 | 518 | The `<dbname>_owner` role is the database owner and should be used when creating
|
519 | 519 | new database objects. All members of the `admin` role, e.g. teams API roles, can
|
520 |
| -become the owner with the `SET ROLE` command. [Default privileges](https://www.postgresql.org/docs/15/sql-alterdefaultprivileges.html) |
| 520 | +become the owner with the `SET ROLE` command. [Default privileges](https://www.postgresql.org/docs/16/sql-alterdefaultprivileges.html) |
521 | 521 | are configured for the owner role so that the `<dbname>_reader` role
|
522 | 522 | automatically gets read-access (SELECT) to new tables and sequences and the
|
523 | 523 | `<dbname>_writer` receives write-access (INSERT, UPDATE, DELETE on tables,
|
@@ -594,7 +594,7 @@ spec:
|
594 | 594 |
|
595 | 595 | ### Schema `search_path` for default roles
|
596 | 596 |
|
597 |
| -The schema [`search_path`](https://www.postgresql.org/docs/15/ddl-schemas.html#DDL-SCHEMAS-PATH) |
| 597 | +The schema [`search_path`](https://www.postgresql.org/docs/16/ddl-schemas.html#DDL-SCHEMAS-PATH) |
598 | 598 | for each role will include the role name and the schemas, this role should have
|
599 | 599 | access to. So `foo_bar_writer` does not have to schema-qualify tables from
|
600 | 600 | schemas `foo_bar_writer, bar`, while `foo_writer` can look up `foo_writer` and
|
@@ -695,7 +695,7 @@ handle it.
|
695 | 695 |
|
696 | 696 | ### HugePages support
|
697 | 697 |
|
698 |
| -The operator supports [HugePages](https://www.postgresql.org/docs/15/kernel-resources.html#LINUX-HUGEPAGES). |
| 698 | +The operator supports [HugePages](https://www.postgresql.org/docs/16/kernel-resources.html#LINUX-HUGEPAGES). |
699 | 699 | To enable HugePages, set the matching resource requests and/or limits in the manifest:
|
700 | 700 |
|
701 | 701 | ```yaml
|
@@ -758,7 +758,7 @@ If you need to define a `nodeAffinity` for all your Postgres clusters use the
|
758 | 758 | ## In-place major version upgrade
|
759 | 759 |
|
760 | 760 | Starting with Spilo 13, operator supports in-place major version upgrade to a
|
761 |
| -higher major version (e.g. from PG 10 to PG 13). To trigger the upgrade, |
| 761 | +higher major version (e.g. from PG 11 to PG 13). To trigger the upgrade, |
762 | 762 | simply increase the version in the manifest. It is your responsibility to test
|
763 | 763 | your applications against the new version before the upgrade; downgrading is
|
764 | 764 | not supported. The easiest way to do so is to try the upgrade on the cloned
|
@@ -838,7 +838,7 @@ spec:
|
838 | 838 | ### Clone directly
|
839 | 839 |
|
840 | 840 | Another way to get a fresh copy of your source DB cluster is via
|
841 |
| -[pg_basebackup](https://www.postgresql.org/docs/15/app-pgbasebackup.html). To |
| 841 | +[pg_basebackup](https://www.postgresql.org/docs/16/app-pgbasebackup.html). To |
842 | 842 | use this feature simply leave out the timestamp field from the clone section.
|
843 | 843 | The operator will connect to the service of the source cluster by name. If the
|
844 | 844 | cluster is called test, then the connection string will look like host=test
|
|
0 commit comments