From: Lamar Owen <lamar.owen@wgcr.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sergio A. Kessler <ser@perio.unlp.edu.ar>
Cc: pgsql-interfaces@postgreSQL.org <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] pg_pwd
Date: Sat, 20 Nov 1999 18:29:44 -0500
Message-ID: <99112018343902.00543@lorc.wgcr.org> (raw)
In-Reply-To: <28767.943138678@sss.pgh.pa.us>
References: <28767.943138678@sss.pgh.pa.us>
On Sat, 20 Nov 1999, Tom Lane wrote:
> As I commented earlier in this thread, I think COPY ought not create
> files with looser permissions than 644 (does anyone know why that's
> not true already?). But that still wouldn't be good enough for pg_pwd.
> Maybe it would be worthwhile to try to force pg_pwd in particular
> to be written with just mode 600. In the standard configuration that
> shouldn't make any difference ...
Hmmm... Can a parameter be passed to COPY giving the file create mode? A
one-time hack to make pg_pwd only do something special sounds inelegant.
>but if people are going to use
> hacked-up initdb code, as you evidently are doing, we probably should
> not rely on the data directory to be locked up tightly...
Just 'initdb --pglib=/usr/lib/pgsql --pgdata=/var/lib/pgsql' /var/lib/pgsql is
created during the rpm installation of the server rpm -- and I can force that
to create mode 0700. HOWEVER, that just fixes the symptom -- not the problem.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: lamar.owen@wgcr.org, tgl@sss.pgh.pa.us, ser@perio.unlp.edu.ar
Subject: Re: [INTERFACES] pg_pwd
In-Reply-To: <99112018343902.00543@lorc.wgcr.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox