postmaster/postgres options assimilation plan

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: postmaster/postgres options assimilation plan
Date: 2006-01-04 15:33:57
Message-ID: 200601041633.58571.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Here's the plan for assimilating the command-line options of the postmaster
and postgres options. I reported earlier on a couple of conflict areas; here
is the full plan:

* Remove: postmaster -a -b -m -M

These options have done nothing forever.

* postmaster options added to postgres: -h -i -k -l -n

These options will not have any useful effects, but their behavior is
consistent if you do, say, SHOW listen_addresses.

* postgres options added to postmaster: -e -E -f -O -P -t -W

Using -E with postmaster does nothing, though.

* Renamed options (because of conflicts):

postgres -N is now postgres -j (mostly internal use)

postgres -o is now postgres -r (mostly internal use)

(postmaster -o is obsolete but still works for compatibility; postgres -o will
get you an error.)

postgres -p is now postgres -y (internal use only)

postmaster -S now sets work_mem, like postgres -S does. The (deprecated)
silent mode can be obtained using the long option --silent-mode=on.

postmaster -s is now postmaster -T (expert/hacker use only)

For the options -O, -P, and -W I have added three new GUC variables
allow_system_table_mods (PGC_SIGHUP), ignore_system_indexes (PGC_BACKEND),
connection_startup_delay (PGC_BACKEND); mostly to simplify the
postmaster->postgres communication.

Except for a few odd exceptions, all command line arguments now map to setting
a GUC variable.

Comments?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-01-04 16:11:15 Re: TRUNCATE, VACUUM, ANALYZE privileges
Previous Message Tino Wildenhain 2006-01-04 14:55:39 Re: psql & readline & win32