Re: [PATCHES] postmaster/postgres merge for testing

From: Marko Kreen <markokr(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] postmaster/postgres merge for testing
Date: 2006-01-24 08:40:51
Message-ID: e51f66da0601240040u283b11ack1736f5ac2bc86dad@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On 1/23/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Attached is a patch that merges postmaster and postgres into just a
> > postmaster command.
>
> I had some second thoughts about this, specifically about which
> direction do we really want to go in. With this patch, it no longer
> really matters what the executable file is named, right? We were both
> implicitly assuming that the name should end up being "postmaster",
> but I think there's a good case to be made that the right thing to do
> is to migrate in the direction of having just one executable named
> "postgres". We've seen complaints before that having a daemon named
> "postmaster" confuses newbies into thinking it's got something to do
> with mail. And it's already the case that the child processes all call
> themselves "postgres", which will become even more confusing if there is
> no longer any executable named "postgres".

+1 for 'postgres'.

--
marko

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2006-01-24 09:03:02 Cache lookup failed error in tsearch2?
Previous Message Christopher Kings-Lynne 2006-01-24 08:21:47 Weird pg_dumpall bug?

Browse pgsql-patches by date

  From Date Subject
Next Message Achilleus Mantzios 2006-01-24 09:06:52 DBMirror.pl performance change
Previous Message Alon Goldshuv 2006-01-24 08:02:20 Libpq COPY optimization patch