>
> "Gregory S. Williamson" <[EMAIL PROTECTED]> wrote:
> > Petr,
> >
> > As long as the new server is the same operating system, and the versions of
> > postgres are the same,
> <...>
>
> As a clarification, 'versions are the same' needs to be more strict than the
> version number (e.g. 8.1.
On Tue, Dec 27, 2005 at 15:49:43 -0800,
"Gregory S. Williamson" <[EMAIL PROTECTED]> wrote:
> Petr,
>
> As long as the new server is the same operating system, and the versions of
> postgres are the same, you can do a binary copy of the data directory and
> move it to the new machine, point the
On Wed, Dec 28, 2005 at 01:00:27AM +0100, Petr wrote:
> I'm try to explain my problems. My customer have Postgre server with any
> older version of my DB (without any new or modified views, functions etc.)
> and when i create export (in pgAdmin3), then pg_dump makes a SQL script. Ok.
> It's nice, b
@postgresql.org
> Subject: Re: [GENERAL] Detaching database
>
> OK.
>
> I'm try to explain my problems. My customer have Postgre server with
any
> older version of my DB (without any new or modified views, functions
etc.)
> and when i create export (in pgAdmin3), then pg_d
OK.
I'm try to explain my problems. My customer have Postgre server with any
older version of my DB (without any new or modified views, functions etc.)
and when i create export (in pgAdmin3), then pg_dump makes a SQL script. Ok.
It's nice, but when i'm trying to run this script on customer's machi
Petr,
As long as the new server is the same operating system, and the versions of
postgres are the same, you can do a binary copy of the data directory and move
it to the new machine, point the new server's postgres to the copied and data
and start it up. Indexes, statistics, etc. all are intac
Pg_dump followed by pg_restore is the usual way:
pg_dump dumps a database as a text file or to other formats.
Usage:
pg_dump [OPTION]... [DBNAME]
General options:
-f, --file=FILENAME output file name
-F, --format=c|t|p outp
