Gabriele Bartolini

That is a known limitation of the "push" method of WAL files. Barman always ships all the available WAL files from the start to the end of the WAL. You...

Hi, On Sun, 15 Nov 2020 at 13:07, sergei lavrov wrote: > Am I right that the barman doesn't have this option right now? > That's correct. It is a...

If the user has specified a separate volume for `walStorage`, verify the settings for `min_wal_size` and `max_wal_size` are coherent. See https://www.postgresql.org/docs/current/runtime-config-wal.html

We could think of an environment variable at the operator level like the following (default): `LOG_FIELDS=level,ts,logger,msg,record,logging_podName` You can remove some of these fields: `LOG_FIELDS=level,ts,logger,msg,record` You can rename fields: `LOG_FIELDS=level:severity,ts:timestamp,logger,msg,record,logging_podName` We...

> TBH I don't think it's in scope for the operator, I expect a good log ingestion system to be able to do that later, e.g. as you would do...

Hi thanks, just to mention that the original PR was co-authored by Leonardo Cecchi as well. Please make sure you mention him (more than me) in the PR. Thanks.

A proposal is to add a new CRD called `PostgresImageCatalog`, like in the following example: ```yaml apiVersion: postgresql.cnpg.io/v1 kind: PostgresImageCatalog metadata: name: postgresql spec: baseName: … versions: - major: “15”...

This should be depending on #12

@francoispqt any news?

Let's get rid of all that logic.