bpineau

Also, I understand we can configure the objects max size (with tune.bufsize). But can we configure the whole cache size (ie. the number of tune.bufsize KB cached objects) ?

gRPC is also a good candidate for end-to-end HTTP/2 :)

Are there plans to support exclusive backups / older PG versions ?

A known (and now fixed) kernel issue affects the scheduler and cgroups subsystem, triggering crashs under kubernetes load (fixed by 754bd598be9bbc9 and 094f469172e00d). The fix was merged in Linux 4.7 (and backported to -stable, in 4.4.70). So if you run an older kernel, maybe you are hit by this?

A few improvments I enjoyed when migrating from Swarm to Kubernetes (older Swarm version, though):

* Namespaces, to group objets and prevent names clashs. Ideal when many devs runs their own copy of the same distributed app from the same manifests and having the same names.

* ConfigMap, to share common configs and project them to files in the containers (and keep them updated in the container, etc), and to provide the configuration separately

* Automatic (EBS, or GCS, or NFS...) volume attachment, ie. to the node hosting your database; and re-attaching elsewhere if the node fails and the database is re-scheduler on an other host. Automated database HA/failover is very nice.

* Ingress manifests, to version the http routing with your app. Though this is very young and incomplete yet.

But yes, k8s is much more complex than Compose (and Swarm), so if the later works for you, changing is probably overkill.

Same here.

No API means no automation, no Chef/Puppet/Ansible/Salt or other kind of scripts. Everything in the head of the person who clicked through the web interface.

Are there automation friendly alternatives?

The stored data format isn't compatible between major versions.

Because of that, upgrades are either stressfull and cumbersome (ie. slony + switchover to a promoted and upgraded slave), or imply a large downtime (ie. pg_upgrade).

Also, because of that (WAL format), you can't use native replication between different major versions of PostgreSQL.

It's just a shorthand for '== 0' (since !0 is true, and !<non-zero> is false). strcmp(3) returns 0 when the two strings are identical. So "if (!strcmp(a, b))" means "if the strings a and b are the same.

Right, and they had to salvage HTTP/2 support (which mandates 128 bit AES) in the process.

The linked post gives an estimation :

> "Tip compiler (with SSA internal checks off) is about 7% slower than go1.6 to compile net/http (go test -a -c -gcflags=-d=ssa/check/off net/http)"

... though we may wonder wether the mesured compiler itself was compiled with or without SSA (with 7% being in the ballpark of the expected SSA gains).

"We now do this consistently: a = malloc(n * sizeof(a));"

Isn't calloc(3) the safer paradigm (protecting against integer overflows, in case n sizeof > SIZE_MAX) recommanded for this case ? (besides the memory zeroing).