Re: language cleanups in code and docs - Mailing list pgsql-hackers

From Andres Freund
Subject Re: language cleanups in code and docs
Date
Msg-id 20200616002342.lyiehw6jjmxqlmac@alap3.anarazel.de
Whole thread Raw
In response to Re: language cleanups in code and docs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: language cleanups in code and docs  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Hi,

On 2020-06-15 19:54:25 -0400, Tom Lane wrote:
> Daniel Gustafsson <daniel@yesql.se> writes:
> > On 15 Jun 2020, at 20:22, Andres Freund <andres@anarazel.de> wrote:
> >> 1) 'postmaster'. As changing that would be somewhat invasive, the word
> >> is a bit more ambiguous, and it's largely just internal, I've left
> >> this alone for now. I personally would rather see this renamed as
> >> supervisor, which'd imo actually would also be a lot more
> >> descriptive. I'm willing to do the work, but only if there's at least
> >> some agreement.
>
> > FWIW, I've never really liked the name postmaster as I don't think it conveys
> > meaning.  I support renaming to supervisor or a similar term.
>
> Meh.  That's carrying PC naming foibles to the point where they
> negatively affect our users (by breaking start scripts and such).
> I think we should leave this alone.

postmaster is just a symlink, which we very well could just leave in
place... I was really just thinking of the code level stuff. And I think
there's some clarity reasons to rename it as well (see comments by
others in the thread).

Anyway, for now my focus is on patches in the series...

- Andres



pgsql-hackers by date:

Previous
From: "tsunakawa.takay@fujitsu.com"
Date:
Subject: RE: [bug?] Is the format of tables in the documentation broken in PG13?
Next
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade fails if vacuum_defer_cleanup_age > 0