Skip site navigation (1) Skip section navigation (2)

initdb problem

From: "Ping (No Magic Asia)" <nattaphol_m(at)nomagicasia(dot)com>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: initdb problem
Date: 2002-07-19 11:16:35
Message-ID: 009c01c22f15$c1b02380$a1efaacb@sirius (view raw or flat)
Thread:
Lists: pgsql-bugs
Hi!

I don't know if it is a bug or not.  What I am facing is that I can't open a database I created.  It's better to explain you by below scenario:

I have installed the Postgres v7.1 or later.  Then, I changed the initial database cluster to another disk, "/mydb".  Then, I changed "PGDATA" in the "/etc/rc.d/init.d/postgresql".  I did change all "start", and "stop" PGDATA variable to "/mydb".  Everything works fine.  

Until I formated the Linux (Redhat, v7.1) system, and re-installed the Redhat (v7.1) again.  Please note that "/mydb" is not been removed because it is kept in another disk.
Now I installed the Postgres v7.1 again, and try to changed the initial database cluster to "/mydb".  And it cannot allow me to do that.    

My point is how can I open my database I kept in "/mydb" again.  Is it a bug?  Please help me.

Sincerely yours,

--
Ping - Nattaphol Manomaiphan. 
EVSD Project Leader
No Magic Asia Ltd., 
719, 22nd Fl., KPN Tower, Rama IX Road, 
Huaykwang, Bangkok 10320 Thailand.
Phone: +66-2-7170252  Fax: +66-2-7170251
email: nattaphol_m(at)nomagicasia(dot)com
http://www.nomagicasia.com

Responses

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2002-07-19 12:22:28
Subject: Bug #715: Too much memory consuming with postmaster
Previous:From: Menno SmitsDate: 2002-07-19 03:06:16
Subject: Re: Bug #714: pg_dump segfaults when given an invalid command

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group