pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lamar Owen <lamar.owen@wgcr.org>
To: pgsql-interfaces@postgreSQL.org <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] pg_pwd
Date: Sat, 20 Nov 1999 23:22:42 -0500
Message-ID: <24903.943158162@sss.pgh.pa.us> (raw)
In-Reply-To: <23778.943151100@sss.pgh.pa.us>

>> Hmmm... Can a parameter be passed to COPY giving the file create mode?

> Yes, that was what I was thinking of.

I have committed changes to current CVS that (a) ensure that pg_pwd
is written with mode 600, (b) reduce the permissions of other files
written by backend-side COPY to 644, instead of 666 as they were;
(c) if initdb is pointed at a pre-existing PGDATA directory, it does
chmod go-rwx on the dir to be sure its permissions are not too loose.
(As a free byproduct, this also verifies that the dir is owned by
postgres...)

I am not 100% comfortable with backpatching these changes into REL6_5,
however, since I had to change the way that the CREATE/ALTER USER
commands invoke COPY.  So I think I will just leave them in the 7.0
code and not back-patch.

As an immediate fix, I suggest regenerating the RH RPMs so that
/var/lib/pgsql is created with mode 700 not 755.

			regards, tom lane



view thread (13+ messages)  latest in thread

Message-ID: <24903.943158162@sss.pgh.pa.us>
Permalink:  ../24903.943158162@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24903.943158162@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, lamar.owen@wgcr.org
  Subject: Re: [INTERFACES] pg_pwd
  In-Reply-To: <24903.943158162@sss.pgh.pa.us>

* 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