Re: Force update_process_title=on in crash recovery? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Force update_process_title=on in crash recovery?
Date
Msg-id 1288021.1600178478@sss.pgh.pa.us
Whole thread Raw
In response to Force update_process_title=on in crash recovery?  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Force update_process_title=on in crash recovery?  (Justin Pryzby <pryzby@telsasoft.com>)
Re: Force update_process_title=on in crash recovery?  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Thomas Munro <thomas.munro@gmail.com> writes:
> Based on a couple of independent reports from users with no idea how
> to judge the progress of a system recovering from a crash, Christoph
> and I wondered if we should override update_process_title for the
> "recovering ..." message, at least until connections are allowed.  We
> already do that to set the initial titles.

> Crash recovery is a rare case where important information is reported
> through the process title that isn't readily available anywhere else,
> since you can't log in.  If you want to gauge  progress on a system
> that happened to crash with update_process_title set to off, your best
> hope is probably to trace the process or spy on the files it has open,
> to see which WAL segment it's accessing, but that's not very nice.

Seems like a good argument, but you'd have to be careful about the
final state when you stop overriding update_process_title --- it can't
be left looking like it's still-in-progress on some random WAL file.
(Compare my nearby gripes about walsenders being sloppy about their
pg_stat_activity and process title presentations.)

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: PG 13 release notes, first draft
Next
From: Amit Langote
Date:
Subject: Re: pg_restore causing deadlocks on partitioned tables