Jiri Popelka
Jiri Popelka
+1 for deprecating `build`. Regarding the upstream Koji builds, whether I need `upstream` or `scratch` in the name depends on whether I have my package maintainer hat on. As a...
I think this has been done since #1212 and packit/packit.dev#269 Feel free to reopen if I'm wrong.
I think this has been done since #1212 and packit/packit.dev#269 Feel free to reopen if I'm wrong.
Still nice to have
Hello @jatindersandhu Have you figured out anything since reporting this? We're seeing this too after moving to a new Openshift cluster and I'm quite clueless.
It's difficult to say what's causing this. We're seeing this on [ROSA](https://docs.openshift.com/rosa), i.e. Openshift 4.8 on AWS. With `postgresql-12-centos7` and `postgresql-13-centos7`. ``` [1] LOG: server process (PID 24643) was terminated...
Experimenting with the probes was the first thing I did and from what I remember I was seeing the problem even without any probe, so the probe shouldn't be a...
> I wonder if we should increase logging reporter of this issue did that, see the first comment
Good point Pavel, thanks. [Managing Kernel Resources](https://www.postgresql.org/docs/current/kernel-resources.html#LINUX-MEMORY-OVERCOMMIT) chapter says: ``` Another approach is to set the process-specific OOM score adjustment value for the postmaster process to -1000, thereby guaranteeing it...
> Experimenting with the probes was the first thing I did and from what I remember I was seeing the problem even without any probe, so the probe shouldn't be...