Re: heads up -- subtle change of behavior of new initdb

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: heads up -- subtle change of behavior of new initdb
Date: 2003-11-14 17:23:21
Message-ID: 3FB50F89.9010004@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:

>Greg Stark <gsstark(at)mit(dot)edu> writes:
>
>
>>I'm not suggesting making that the default setup, just loosening the
>>paranoia check so that if an admin sets the directory to be group
>>readable the database doesn't refuse to start up.
>>
>>
>
>In previous discussions of this point, paranoia was considered desirable.
>I don't think the situation has changed.
>
>
>
Would it be worth having a command line option to relax the paranoia a
bit, leaving the current paranoia setting as the default? I guess it
would have to be on the command line because IIRC this is checked before
we ever look at the config file.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-11-14 17:26:34 Re: [HACKERS] heads up -- subtle change of behavior of new initdb
Previous Message Tom Lane 2003-11-14 17:21:36 Re: [HACKERS] heads up -- subtle change of behavior of new initdb

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2003-11-14 17:26:34 Re: [HACKERS] heads up -- subtle change of behavior of new initdb
Previous Message Tom Lane 2003-11-14 17:21:36 Re: [HACKERS] heads up -- subtle change of behavior of new initdb