From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Dominique Devienne <ddevienne@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Using PostgreSQL for service discovery and health-check
Date: Thu, 9 Feb 2023 09:46:41 -0800
Message-ID: <66d8dfb6-c709-90a3-71a5-1d51f89db0df@aklaver.com> (raw)
In-Reply-To: <CAFCRh-_mR=3T0ApqjjvCT6N9YYgSWsph2bGZqkGax2+8jhmoaw@mail.gmail.com>
References: <CAFCRh-9okm64gEM-Oy27Lh-2k=PKEBbK1C5cG1vgwEjgN-EB+w@mail.gmail.com>
<a7bc901a-a191-9504-c5be-41de7128c5b9@aklaver.com>
<CAFCRh--5bphNNK2VV6icO37OnY0tZ2rTqTroJEr8LqabjUxBcQ@mail.gmail.com>
<eea6ff37-a174-deac-11b4-8a590fedbdc9@aklaver.com>
<CAFCRh-_mR=3T0ApqjjvCT6N9YYgSWsph2bGZqkGax2+8jhmoaw@mail.gmail.com>
On 2/9/23 09:40, Dominique Devienne wrote:
> On Thu, Feb 9, 2023 at 5:51 PM Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.com>> wrote:
>
> On 2/9/23 08:16, Dominique Devienne wrote:
> > On Thu, Feb 9, 2023 at 5:05 PM Adrian Klaver
> <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
> The flip side of that is that with known ports it would it easier to
> have a process on the Postgres machine or in the database that checks
> the ports on regular basis. And as part of that process mark any non
> responding ports as inactive. That would solve the zombie problem.
>
>
> That's one possibility. But the "reaper" process could just as well scan
> the service table,
> and probe those too. So again, I'm not sure what the fixed-port approach
> gains me, beside
> perhaps the reaper not having to connect to PostgreSQL itself. I'm OK
> with connecting.
What is the reaper process?
>
> Thanks for the your input. Always good to have one's arguments
> challenged by experts.
--
Adrian Klaver
adrian.klaver@aklaver.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: adrian.klaver@aklaver.com, ddevienne@gmail.com
Subject: Re: Using PostgreSQL for service discovery and health-check
In-Reply-To: <66d8dfb6-c709-90a3-71a5-1d51f89db0df@aklaver.com>
References: <CAFCRh-9okm64gEM-Oy27Lh-2k=PKEBbK1C5cG1vgwEjgN-EB+w@mail.gmail.com> <a7bc901a-a191-9504-c5be-41de7128c5b9@aklaver.com> <CAFCRh--5bphNNK2VV6icO37OnY0tZ2rTqTroJEr8LqabjUxBcQ@mail.gmail.com> <eea6ff37-a174-deac-11b4-8a590fedbdc9@aklaver.com> <CAFCRh-_mR=3T0ApqjjvCT6N9YYgSWsph2bGZqkGax2+8jhmoaw@mail.gmail.com> <66d8dfb6-c709-90a3-71a5-1d51f89db0df@aklaver.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox