pg_dump

From: "Adam Lang" <aalang(at)rutgersinsurance(dot)com>
To: "Brook Milligan" <brook(at)biology(dot)nmsu(dot)edu>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: pg_dump
Date: 2000-08-29 18:01:47
Message-ID: 013f01c011e3$32ff1480$330a0a0a@Adam
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Also, is pg_dump good for backing up a database or should I use another
means? (I did read the part about partial indices and large objects not
supported.)

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Brook Milligan" <brook(at)biology(dot)nmsu(dot)edu>
To: <aalang(at)rutgersinsurance(dot)com>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: Tuesday, August 29, 2000 12:28 PM
Subject: Re: [GENERAL] SQL scripts - sequences

> My solution in a similar situation is to have a bunch of scripts to
> drop/create the tables/functions/views/triggers/... needed. Use
> pg_dump to dump just the data (not the schema) but include the -c flag
> (I use -a -c -D) so that sequences are dropped and recreated with the
> right values. To reload: run pg_dump -a -c -D, run your scripts
> (which drop and recreate the data structures, then run your pg_dump
> output through psql to reload the data. Sequences and tables will
> agree fine.
>
> Cheers,
> Brook

In response to

Browse pgsql-general by date

  From Date Subject
Next Message funk101 2000-08-29 18:06:30 lo_import
Previous Message Ross J. Reedstrom 2000-08-29 18:00:13 Re: foreign keys - script