On Sun, 2024-02-25 at 10:50 +0200, Gena Makhomed wrote:
> Previously posted to pgsql-bugs mail list asBUG #18361, but as I understand later, this may not be the PostgreSQL bug
itself,but it may be the rpm/yum/dnf packaging bug?
>
> Can you please help to fix this bug, or find a workaround?
>
> Because killing postgres via SIGKILL is not a good idea.
>
>
> ---------- Forwarded message ---------
> Bug reference: 18361
> PostgreSQL version: 16.2
> Operating system: Rocky Linux release 9.3
>
> PostgreSQL 16.2 installed on the Rocky Linux release 9.3 server from
> official repository with official instruction from page
> https://www.postgresql.org/download/linux/redhat/
>
> when I execute command
>
> # systemctl stop postgresql-16.service ; systemctl status
> postgresql-16.service
>
> I see, what PostgreSQL 16.2 was killed by SIGKILL.
>
> this is a bug, as I understand, because database will be corrupted.
>
> Is it possible to fix this bug and stop killing PostgreSQL with signal
> SIGKILL ?
>
> Feb 24 12:47:19 postgres-16.example.net systemd[1]: Stopping PostgreSQL 16 database server...
> Feb 24 12:47:19 postgres-16.example.net systemd[1]: postgresql-16.service: Killing process 26672 (postgres) with
signalSIGKILL.
> Feb 24 12:47:19 postgres-16.example.net systemd[1]: postgresql-16.service: Deactivated successfully.
> Feb 24 12:47:19 postgres-16.example.net systemd[1]: Stopped PostgreSQL 16 database server.
Strange. In my "postgresql-16.service", I find
TimeoutStopSec=1h
which should make systemd wait for an hour after sending SIGTERM before it
uses SIGKILL. Is your setting different?
> Please consider the environment before printing
Aww. I would have liked to make a poster from it.
Yours,
Laurenz Albe