Sorry guys, was my mistake... I found one file missing in global
tablespace. Copying it there fixed the problem.
Thanks everyone!
On Mon, 2007-12-24 at 14:07 -0800, Richard Broersma Jr wrote:
> --- On Mon, 12/24/07, Alex Vinogradovs <[EMAIL PROTECTED]> wrote:
>
> > P.S. datafiles are 85GB in s
--- On Mon, 12/24/07, Alex Vinogradovs <[EMAIL PROTECTED]> wrote:
> P.S. datafiles are 85GB in size, I couldn't really dump
> and restore...
Don't for get the steps of compressing and uncompressing between dump and
restore.;) If the file is still too big, you can always use tar to spit the
fil
I expect that it is not quite as easy as that.
My advice (as a non-expert) would be to install the same version of pg
onto the target machine, and use etl
(http://en.wikipedia.org/wiki/Extract,_transform,_load) to transfer the
data. Basically you just need a small script (I like PHP myself, bu
Guys,
I've created a copy of my database to run on a different server
by copying entire data directory while database instance was stopped.
Database generally works on the target machine, but I'm getting
following error when trying to create a plpgsql function :
ERROR: could not open relation 166
