From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsqlrpms-hackers(at)pgfoundry(dot)org |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [Pgsqlrpms-hackers] Safer auto-initdb for RPM init script |
Date: | 2006-08-25 14:45:35 |
Message-ID: | 24279.1156517135@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Reinhard Max <max(at)suse(dot)de> writes:
> Another flaw of the flag-file method is, that PGDATA might have been
> changed by the sysadmin between installing the RPM and calling the
> init script for the first time.
What problem do you see there? With either of these methods, a manual
change in PGDATA would require a manual initdb before the postmaster
would start. That seems like a good conservative thing to me.
(Actually, with the flag-file method you could get the initscript
to run initdb for you by hand-creating the flag file, but it seems
unlikely people would do that in practice.)
> But shouldn't mountpoints always have 000 permissions to prevent
> writing into the directory as long as nothing is mounted to it?
Not sure that that helps much given that the initscript runs as root.
And in any case the point here is to protect against human error,
not to assume that the installation is managed according to very
best practices.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2006-08-25 14:49:57 | Re: Safer auto-initdb for RPM init script |
Previous Message | Peter Eisentraut | 2006-08-25 14:44:55 | Re: [Pgsqlrpms-hackers] Safer auto-initdb for RPM init |