Re: Remove behaviour of postmaster -o

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Andy Chambers <andychambers2002(at)yahoo(dot)co(dot)uk>
Subject: Re: Remove behaviour of postmaster -o
Date: 2006-05-09 03:20:18
Message-ID: 4127.1147144818@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane wrote:
>> Not sure why Peter didn't continue working on it.

> I'm still working on the postmaster/postgres merge. But the behavior of
> postmaster -o is not going to be removed. That TODO item might be
> appropriate in a release or three at best.

I think the point though is that -o becomes a no-op: whether you put -o
in front of some options won't matter anymore, because they'll be
interpreted the same either way.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message PFC 2006-05-09 08:38:17 Big IN() clauses etc : feature proposal
Previous Message Klint Gore 2006-05-09 00:10:19 Re: performance question (something to do w/ parameterized