Philip Haberkern

> This is exactly what postgres-operator avoids: every time you deploy a new cluster it gets a new and unique archive location. That is, we will never have the situation...

> > you can specify that there should be no prefix and suffix within the archive location path (S3), which leads to a location which only holds the cluster name...

But wouldn't it make sense anyway for having an overview which Spilo image uses which minor for history reasons? Maybe someone wants to use a specific PG version or Spilo...

We have this issue recently too. There are no obvious changes. For us the following applies: - When killing a replica pod, it will try to startup and bootstrap from...

An update from my side. In our case, the issue was on S3 storage side. The Object Storage falsely replied with error code `500` instead of `404` when an object...

> > An update from my side. In our case, the issue was on S3 storage side. The Object Storage falsely replied with error code `500` instead of `404` when...

Having the possibility to give an order or priority to the modrules would be a good solution.

> Lets go straight to 3.15. This is also what we use for the pooler. Can you raise the version in all Docker files of the project that use it...

> @FxKu @thedatabaseme - can we bump the base image to 3.16 @pgvishnuram @FxKu This has to be approved by the maintainers anyway. Just tell me what you wish for.

@puneet2715 Are those images you've attached created by yourself or did you copy / download them somewhere? Apart from that, I've changed the subject of this PR in order to...