Re: kevent latch paths don't handle postmaster death well

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: kevent latch paths don't handle postmaster death well
Date: 2020-10-14 19:40:31
Message-ID: 3625898.1602704431@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> The process exit event is like an 'edge', not a 'level'... hmm. It
> might be enough to set report_postmaster_not_running = true the first
> time it tells us so if we try to wait again we'll treat it like a
> level. I will look into it later today.

Seems like having that be per-WaitEventSet state is also not a great
idea --- if we detect PM death while waiting on one WES, and then
wait on another one, it won't work. A plain process-wide static
variable would be a better way I bet.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2020-10-14 20:10:22 Re: kevent latch paths don't handle postmaster death well
Previous Message Justin Pryzby 2020-10-14 19:39:00 jit and explain nontext