Re: Should we improve "PID XXXX is not a PostgreSQL server process" warning for pg_terminate_backend(<<postmaster_pid>>)?

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Should we improve "PID XXXX is not a PostgreSQL server process" warning for pg_terminate_backend(<<postmaster_pid>>)?
Date: 2022-01-11 18:07:52
Message-ID: E053E257-E99F-46A6-B2EF-C0E4BB1F6398@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/11/22, 10:06 AM, "John Naylor" <john(dot)naylor(at)enterprisedb(dot)com> wrote:
> I pushed this with one small change -- I felt the comment didn't need
> to explain the warning message, since it now simply matches the coding
> more exactly. Also, v5 was a big enough change from v4 that I put
> Nathan as the first author.

Thanks!

Nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2022-01-11 18:38:10 Re: fix crash with Python 3.11
Previous Message John Naylor 2022-01-11 18:03:24 Re: Should we improve "PID XXXX is not a PostgreSQL server process" warning for pg_terminate_backend(<<postmaster_pid>>)?