| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Karl O(dot) Pinc" <kop(at)karlpinc(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Devrim Gündüz <devrim(at)gunduz(dot)org>, Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: drop postmaster symlink |
| Date: | 2023-01-07 23:38:25 |
| Message-ID: | 3492787.1673134705@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Karl O. Pinc" <kop(at)karlpinc(dot)com> writes:
> This is a review of Peter's 2 patches. I see only 1 small problem.
> Looking at the documentation, a "postmaster" in the glossary is
> defined as the controlling process. This works; it needs to be called
> something. There is still a postmaster.pid (etc.) in the data
> directory.
> The word "postmaster" (case insensitive) shows up 84 times in the
> documentation. I looked at all of these.
Hmm ... I thought this patch was about getting rid of the
admittedly-obsolete installed symlink. If it's trying to get rid of
the "postmaster" terminology for our parent process, I'm very strongly
against that, either as regards to code or documentation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2023-01-07 23:41:29 | Re: pgsql: Delay commit status checks until freezing executes. |
| Previous Message | Noah Misch | 2023-01-07 23:29:24 | FYI: 2022-10 thorntail failures from coreutils FICLONE |