Re: Using PostgreSQL for service discovery and health-check

Поиск
Список
Период
Сортировка
От Dominique Devienne
Тема Re: Using PostgreSQL for service discovery and health-check
Дата
Msg-id CAFCRh-_mR=3T0ApqjjvCT6N9YYgSWsph2bGZqkGax2+8jhmoaw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Using PostgreSQL for service discovery and health-check  (Adrian Klaver <adrian.klaver@aklaver.com>)
Ответы Re: Using PostgreSQL for service discovery and health-check  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: Using PostgreSQL for service discovery and health-check  (Adrian Klaver <adrian.klaver@aklaver.com>)
Список pgsql-general
Дерево обсуждения
On Thu, Feb 9, 2023 at 5:51 PM Adrian Klaver <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
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.

Thanks for the your input. Always good to have one's arguments challenged by experts.

В списке pgsql-general по дате отправления:

Предыдущее
От: Dominique Devienne
Дата:
Сообщение: Re: WHERE col = ANY($1) extended to 2 or more columns?
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: Using PostgreSQL for service discovery and health-check