Re: Let's make PostgreSQL multi-threaded

On Thu, Jun 8, 2023 at 3:00 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
>

> Yea, we definitely need the supervisor function in a separate
> process. Presumably that means we need to split off some of the postmaster
> responsibilities - e.g. I don't think it'd make sense to handle connection
> establishment in the supervisor process. I wonder if this is something that
> could end up being beneficial even in the process world.
>
> A related issue is that we won't get SIGCHLD in the supervisor process
> anymore. So we'd need to come up with some design for that.

If we fork the main Postgres process from the supervisor process then
any exit to the main process will send SIGCHLD in the supervisor
process, right? I agree we can handle all connection establishment
and other thread-related stuff in the main Postgres process. But I
assume this main process should be forked out of the supervisor
process.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com