Re: SQL scripts - sequences - Mailing list pgsql-general

From Adam Lang
Subject Re: SQL scripts - sequences
Date
Msg-id 012b01c011de$d18462e0$330a0a0a@Adam
Whole thread Raw
In response to SQL scripts - sequences  ("Adam Lang" <aalang@rutgersinsurance.com>)
Responses Re: SQL scripts - sequences  (Brook Milligan <brook@biology.nmsu.edu>)
List pgsql-general
Oh wow (after reading over pg_dump and trying it).  I didn't know about
that.  That's very nice.

Is it safe and accurate?  Should I be able to feel mostly secure about using
that to dump my database definitions?

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Brook Milligan" <brook@biology.nmsu.edu>
To: <aalang@rutgersinsurance.com>
Cc: <pgsql-general@postgresql.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


pgsql-general by date:

Previous
From: Emile D Snyder
Date:
Subject: replacement for LEFT JOIN in mysql->postres changeover?
Next
From: "Adam Lang"
Date:
Subject: foreign keys - script