In article <C19E2E1F.5D22D%scott_ribe@killerbytes.com>,
scott_ribe@killerbytes.com says...
> >>>> Uh, do you have the entier /data directory tree? If so, just restore
> >>>> the directory start it up a binary.
> >>>>
> >>>>
> >>>
> >>> Yes I have the entire dir/file set. But what does "If so, just restore
> >>> the directory start it up a binary" mean? Restore the dir, you mean copy
> >>> it to it's location under \base? What does start it up a(s?) binary
> >>> mean? I'm new to postgres.
> >>>
> >>> I have copied the folders back to the base dir (like C:\PostgreSQL\data
> >>> \base\16404) if that's step one but what after that?
>
> OK, one more try:
>
> - Stop postgres.
>
> - Restore the ***ENTIRE*** ***data*** directory tree. Not "base", not
> something else "to it's location under \base". The entire data directory
> tree, just like the helpful message said.
>
> - Start postgres.
>
> Now, if you did that, and the raw files were from the same OS & architecture
> & postgres build settings, everything is fine. Otherwise, you're out of
> luck.
>
> > I see...I'm using pgAdmin III with 8.1.5, and the dbs don't reappear in
> > the pgAdmin list of databases automatically.
>
> I doubt that.
>
>
Via Patrick's post I realized what my misstep was, but unforutnately it
has not resulted in a restored database in my case, I'm not sure why.
But thanks for the pointer, I'm sure what you've written is correct,
there is just some condition that prevents success in this case. It is
same OS, exact version of Postgres, everything that I'm aware of is a
match, but something is obviously at variance.