Skip site navigation (1) Skip section navigation (2)

Re: pg_config, pg_service.conf, postgresql.conf ....

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: "Mark Woodward" <pgsql(at)mohawksoft(dot)com>
Subject: Re: pg_config, pg_service.conf, postgresql.conf ....
Date: 2006-02-21 14:27:38
Message-ID: 200602211527.38803.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-hackers
Mark Woodward wrote:
> The pg_config program needs to display more information, specifically
> where the location of pg_service.conf would reside.

pg_config --sysconfdir

> Also, I know I've been harping on this for years (literally), but
> since the PosgteSQL programs already have the notion that there is
> some static directory for which to locate files (pg_service.conf),
> couldn't we also use this directory to include pg_hba.conf,
> pg_ident.conf, and perhaps even postgresql.conf?

Considering that pg_service.conf is a client configuration file and the 
others are server configuration files, I don't think there is a causal 
relationship between putting them one place or another, independent of 
the individual merit of placing them in particular spot.  I'm not sure 
that sentence makes sense.

> Maybe we also add to pg_service.conf enough data to start a database
> so that a tool, perhaps pg_service, could read and extract the info
> for pg_ctl, so databases can be started by service names:
>
> pg_ctl -S service_name start

I don't mind a mechanism that pg_ctl can start more than one database 
cluster.  The Debian packages have started to develop such a system 
independently because of upgrading requirements, but putting it into 
the mainline would certainly be useful.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

pgsql-hackers by date

Next:From: Martijn van OosterhoutDate: 2006-02-21 14:36:13
Subject: Re: pg_config, pg_service.conf, postgresql.conf ....
Previous:From: Andrew DunstanDate: 2006-02-21 13:36:48
Subject: windows / initdb oddness

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group