pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Gena Makhomed <makhomed@gmail.com>
To: pgsql-pkg-yum@lists.postgresql.org
Subject: Re: systemd[1]: postgresql-16.service: Killing process 25992 (postgres) with signal SIGKILL.
Date: Mon, 26 Feb 2024 10:19:09 +0100
Message-ID: <c2a5a6287dc8a0677f44f5c4b7da294d50b32d7f.camel@cybertec.at> (raw)
In-Reply-To: <CAKYxhBmpx8-ch_38EprbEMu3G3sYm=-eZUySLzW5xP3B1bexuw@mail.gmail.com>
References: <18361-1a3f843f5f6ce694@postgresql.org>
	<CAKYxhBmpx8-ch_38EprbEMu3G3sYm=-eZUySLzW5xP3B1bexuw@mail.gmail.com>

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 signal SIGKILL.
> 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





view thread (4+ messages)  latest in thread

Message-ID: <c2a5a6287dc8a0677f44f5c4b7da294d50b32d7f.camel@cybertec.at>
Permalink:  ../c2a5a6287dc8a0677f44f5c4b7da294d50b32d7f.camel@cybertec.at/
Also on:    postgresql.org/message-id/c2a5a6287dc8a0677f44f5c4b7da294d50b32d7f.camel@cybertec.at

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: laurenz.albe@cybertec.at, makhomed@gmail.com, pgsql-pkg-yum@lists.postgresql.org
  Subject: Re: systemd[1]: postgresql-16.service: Killing process 25992 (postgres) with signal SIGKILL.
  In-Reply-To: <c2a5a6287dc8a0677f44f5c4b7da294d50b32d7f.camel@cybertec.at>
  References: <18361-1a3f843f5f6ce694@postgresql.org> <CAKYxhBmpx8-ch_38EprbEMu3G3sYm=-eZUySLzW5xP3B1bexuw@mail.gmail.com> <c2a5a6287dc8a0677f44f5c4b7da294d50b32d7f.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox