Re: What is the motivation of include directive and

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Takayuki Tsunakawa <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: What is the motivation of include directive and
Date: 2007-01-17 03:47:15
Message-ID: 200701170347.l0H3lFf23540@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Takayuki Tsunakawa wrote:
> Hello,
>
> Let me ask about the background of configuration files. I couldn't
> find the relevant information in the 8.2 documentation. I'm sorry to
> cause you trouble.
>
> In section "17.1. Setting Parameters", include directive is described.
> Why was this directive prepared? What usage is assumed? Is it for
> GUI tools, or for placing custom parameters in other files?
>
> In section "17.2. File Locations", the following parameters are
> described:
>
> data_directory (string)
> config_file (string)
> hba_file (string)
> ident_file (string)
> external_pid_file (string)
>
> What demand is assumed for placing configuration files outside the
> data directory? Is it for placing configuration files in /etc to
> conform to the FHS (Filesystem Hierarchy Standard, as documented
> below) to enable the backup of all configuration files on the system?

It was designed for people who have multiple postmasters, but and want
to centralize some of that configuation.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-01-17 03:54:09 Re: float8 width_bucket function
Previous Message Tom Lane 2007-01-17 03:24:10 Re: Idea for fixing the Windows fsync problem