initdb problem - Mailing list pgsql-bugs

From Ping (No Magic Asia)
Subject initdb problem
Date
Msg-id 009c01c22f15$c1b02380$a1efaacb@sirius
Whole thread Raw
Responses Re: initdb problem
List 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 d=
atabase 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.=20=20

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

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

Sincerely yours,

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

pgsql-bugs by date:

Previous
From: Menno Smits
Date:
Subject: Re: Bug #714: pg_dump segfaults when given an invalid command
Next
From: Mike Coleman
Date:
Subject: pg_ctl failure with older Bourne shells (use ${1:+"$@"})