On Fri, Aug 25, 2006 at 07:21:50AM -0700, Joe Conway wrote:
We also decided to turn off the init script execution entirely. The DBAs
were more comfortable with a manual database startup for a production
machine anyway (this is the way they typically handle Oracle databases
also). They get
Jim C. Nasby wrote:
On Fri, Aug 25, 2006 at 07:21:50AM -0700, Joe Conway wrote:
We also decided to turn off the init script execution entirely. The DBAs
were more comfortable with a manual database startup for a production
machine anyway (this is the way they typically handle Oracle databases
On Sat, Aug 26, 2006 at 01:32:17PM -0700, Joshua D. Drake wrote:
Jim C. Nasby wrote:
On Fri, Aug 25, 2006 at 07:21:50AM -0700, Joe Conway wrote:
We also decided to turn off the init script execution entirely. The DBAs
were more comfortable with a manual database startup for a production
Jim C. Nasby wrote:
On Fri, Aug 25, 2006 at 07:21:50AM -0700, Joe Conway wrote:
We also decided to turn off the init script execution entirely. The DBAs
were more comfortable with a manual database startup for a production
machine anyway (this is the way they typically handle Oracle
Jim C. Nasby wrote:
On Sat, Aug 26, 2006 at 01:32:17PM -0700, Joshua D. Drake wrote:
I am not exactly sure why we initdb at all. IMHO it would be better if
the start script just checked if there was a cluster. If not, it
wouldn't start, it would error with: You do not have a cluster, please
Matthew T. O'Connor wrote:
Jim C. Nasby wrote:
On Sat, Aug 26, 2006 at 01:32:17PM -0700, Joshua D. Drake wrote:
I am not exactly sure why we initdb at all. IMHO it would be better
if the start script just checked if there was a cluster. If not, it
wouldn't start, it would error with: You do
Joshua D. Drake wrote:
Matthew T. O'Connor wrote:
Jim C. Nasby wrote:
As Tom mentioned, it's for newbie-friendliness. While I can understand
that, I think it needs to be easy to shut that off.
I understand that, but it seems the whole problem of people
overwriting there data dir is because
Jim C. Nasby wrote:
On Fri, Aug 25, 2006 at 07:21:50AM -0700, Joe Conway wrote:
We also decided to turn off the init script execution entirely. The DBAs
were more comfortable with a manual database startup for a production
machine anyway (this is the way they typically handle Oracle
Alvaro Herrera wrote:
Jim C. Nasby wrote:
On Fri, Aug 25, 2006 at 07:21:50AM -0700, Joe Conway wrote:
We also decided to turn off the init script execution entirely. The DBAs
were more comfortable with a manual database startup for a production
machine anyway (this is the way they
Andrew Dunstan wrote:
Alvaro Herrera wrote:
This is trivial to do --- just add a /etc/some_dir/postgresql file
that contains a line like
AUTO_INITDB=0
to turn the auto-initdb'ing feature of the init script off. If the file
is not present or AUTO_INITDB is not defined to zero in that
Tom Lane wrote:
We've seen more than one report of corruption of PG databases that
seemed to be due to the willingness of the RPM init script to run
initdb if it thinks the data directory isn't there. This is pretty
darn risky on an NFS volume, for instance, which might be offline
at the
11 matches
Mail list logo
