From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PostmasterContext survives into parallel workers!? |
Date: | 2016-08-01 23:21:23 |
Message-ID: | 21256.1470093683@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> Personally I think the whole logic should be reworked so we do most of
> that that only from one place.
Alvaro already mentioned a couple of reasons why that might not be so
easy.
> Especially the signal handler stuff
> should imo just be replaced by setting latch, which then does the work
> inside the normal main loop.
Of course, then we're utterly dependent on the latch logic to be
zero-failure, as any bug in it takes out the postmaster. That idea
would've been rejected out of hand earlier in the development of
the latch code. Maybe it's safe enough today, but I still wonder what
it is that we're buying after we do such a massive rewrite of the
postmaster.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2016-08-01 23:27:25 | Re: PostmasterContext survives into parallel workers!? |
Previous Message | Andres Freund | 2016-08-01 22:54:35 | Re: PostmasterContext survives into parallel workers!? |