Re: postmaster/postgres options assimilation plan

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
Subject: Re: postmaster/postgres options assimilation plan
Date: 2006-01-04 16:40:02
Message-ID: 3300.1136392802@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:
> Here's the plan for assimilating the command-line options of the postmaster
> and postgres options.
> ...

> * 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.

Did you mean -N rather than -n here?

> 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.

Might as well let allow_system_table_mods be PGC_BACKEND too. The
dangers it poses are not made less by turning it on in all backends
at the same time.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2006-01-04 19:10:29 Improving N-Distinct estimation by ANALYZE
Previous Message Tom Lane 2006-01-04 16:11:15 Re: TRUNCATE, VACUUM, ANALYZE privileges