Search Postgresql Archives

Re: Using PostgreSQL for service discovery and health-check

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2/9/23 09:40, Dominique Devienne wrote:
On Thu, Feb 9, 2023 at 5:51 PM Adrian Klaver <adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>> wrote:

    On 2/9/23 08:16, Dominique Devienne wrote:
     > On Thu, Feb 9, 2023 at 5:05 PM Adrian Klaver
    <adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>
    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@xxxxxxxxxxx






[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]

  Powered by Linux