Re: A new function to wait for the backend exit after termination

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "Hou, Zhijie" <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Muhammad Usama <m(dot)usama(at)gmail(dot)com>
Subject: Re: A new function to wait for the backend exit after termination
Date: 2021-06-14 16:46:34
Message-ID: 20210614164634.GH31772@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 14, 2021 at 09:40:27AM -0700, Noah Misch wrote:
> > > Agreed, these strings generally give less detail. I can revert that to the
> > > v13 wording, 'terminate a server process'.

...

> > Maybe you'd also update the release notes.
>
> What part of the notes did you expect to change that the patch did not change?

Sorry, I didn't notice that your patch already adjusted the v14 notes.

Note that Bharath also corrected your commit message to say "unable *to*", and
revert the verbose pg_proc.dat descr change.

Thanks,
--
Justin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2021-06-14 16:49:19 Re: array_cat anycompatible change is breaking xversion upgrade tests (v14 release notes)
Previous Message Andrew Dunstan 2021-06-14 16:41:36 Re: recent failures on lorikeet