Re: wait event and archive_command

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: wait event and archive_command
Date: 2021-10-22 09:32:23
Message-ID: YXKFJ1AeFXa3/M9g@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 21, 2021 at 10:57:50PM +0900, Fujii Masao wrote:
> Also how about adding wait events for other commands like
> archive_cleanup_command, restore_command and recovery_end_command?

+1 to add something for all of them as we track the startup process in
pg_stat_activity. Thinking with a larger picture, this comes down to
the usage of system(). We could introduce a small wrapper of system()
that takes as argument a wait event for the backend.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vladimir Sitnikov 2021-10-22 09:46:38 Re: Adding CI to our tree
Previous Message Michael Paquier 2021-10-22 09:24:36 Re: [PATCH] Fix memory corruption in pg_shdepend.c