Skip to content

Commit bb38ea1

Browse files
committed
Merge pull request sorintlab#532 from sgotti/release_v0.12.0
Release v0.12.0
2 parents bc5813d + ca98152 commit bb38ea1

File tree

2 files changed

+20
-7
lines changed

2 files changed

+20
-7
lines changed

CHANGELOG.md

Lines changed: 18 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,22 @@
11
### v0.12.0
22

3-
## Upgrades notes.
3+
#### New features
4+
5+
* Detect and report when keeper persistent data dir is not the expected one (usually due to wrong configuration, non persistent storage etc...) ([#510](https://github.com/sorintlab/stolon/pull/510))
6+
* Support PostgresSQL 11 (beta) ([#513](https://github.com/sorintlab/stolon/pull/513))
7+
* Replication slots declared in the clusterspec `additionalMasterReplicationSlots` option will now be prefixed with the `stolon_` string to let users be able to manually create/drop custom replication slots (See Upgrade Notes) ([#531](https://github.com/sorintlab/stolon/pull/531))
8+
9+
#### Bug Fixes
10+
11+
* fix wrong address in pg_hba.conf when clusterspec `defaultSUReplAccessMode` is `strict` ([#520](https://github.com/sorintlab/stolon/pull/520))
12+
13+
and [many other](https://github.com/sorintlab/stolon/milestone/11) bug fixes and documentation improvements.
14+
15+
Thanks to everybody who contributed to this release:
16+
17+
Alexandre Assouad, Lothar Gesslein, @nseyvet
18+
19+
#### Upgrades notes.
420

521
* Replication slots declared in the clusterspec `additionalMasterReplicationSlots` option will now be prefixed with the `stolon_` string to let users be able to manually create/drop custom replication slots (they shouldn't start with `stolon_`). Users of these feature should upgrade all the references to these replication slots adding the `stolon_` prefix.
622

@@ -24,7 +40,7 @@ Thanks to everybody who contributed to this release:
2440
Bill Helgeson, Niklas Hambüchen, Sylvere Richard, Tyler Kellen
2541

2642

27-
## Upgrades notes.
43+
#### Upgrades notes.
2844

2945
* In the k8s store backend, the label that defines the kind of stolon component has changed from `app` to `component`. When upgrading you should update the various resource descriptors setting the k8s component name (`stolon-keeper`, `stolon-sentinel`, `stolon-proxy`) inside the `component` label instead of the `app` label.
3046
* When using the etcdv2 store, due to a wrong leader election path introduced in the last release and now fixed, if your sentinel returns an election error like `election loop error {"error": "102: Not a file ...` you should stop all the sentinels and remove the wrong dir using `etcdctl rmdir /stolon/cluster/$STOLONCLUSTER/sentinel-leader` where `$STOLONCLUSTER` should be substituted with the stolon cluster name (remember to set `ETCDCTL_API=2`).

README.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -52,14 +52,11 @@ Anyway it's quite easy to reset a cluster from scratch keeping the current maste
5252

5353
## Requirements
5454

55-
* PostgreSQL 10 or 9 (9.4, 9.5, 9.6)
56-
* etcd2 >= v2.0, etcd3 >= v3.0, consul >= v0.6 or kubernetes 1.8 (based on the store you're going to use)
57-
55+
* PostgreSQL 11, 10 or 9 (9.4, 9.5, 9.6)
56+
* etcd2 >= v2.0, etcd3 >= v3.0, consul >= v0.6 or kubernetes >= 1.8 (based on the store you're going to use)
5857

5958
* OS: currently stolon is tested on GNU/Linux (with reports of people using it also on Solaris, *BSD and Darwin)
6059

61-
62-
6360
## build
6461

6562
To build stolon we usually test and support the latest two major versions of Go like in the [Go release policy](https://golang.org/doc/devel/release.html#policy).

0 commit comments

Comments
 (0)