Re: dumping table contents in a sensible order

Chris Withers <chris(at)simplistix(dot)co(dot)uk> writes:

> Hi All,
>
> I have a database that I want to dump three tables from, for use in
> development. They form a subset of the data, so I was dumping like
> this:
>
> pg_dump thedatabase --inserts -t table_one -t depends_on_table_one -t
> depends_on_previous_two > dump.sql
>
> However, when I try to load this using the following:
>
> psql thedatabase_dev < dump.sql
>
> I get the following:
>
> SET
> ERROR: unrecognized configuration parameter "lock_timeout"

You are using a higher version numbered pg_dump than the target system.

For best results...

origin-systemversion <= target-system-version
pg-dump-version == target-system-version

HTH

> SET
> SET
> SET
> SET
> ERROR: unrecognized configuration parameter "row_security"
> SET
> SET
> SET
> ERROR: relation "table_one" already exists
> ALTER TABLE
> ERROR: relation "depends_on_previous_two" already exists
> ALTER TABLE
> ERROR: relation "depends_on_previous_two_id_seq" already exists
> ALTER TABLE
> ALTER SEQUENCE
> ALTER TABLE
> INSERT 0 1
> ...
> INSERT 0 1
> ERROR: insert or update on table "table_one" violates foreign key
> constraint "table_one_parent_id_fkey"
> DETAIL: Key (parent_id)=(xxx) is not present in table "table_one".
>
> So, the problem appears to be that table_one is self-referential by
> way of a parent_id field.
>
> How can I either:
>
> - dump the table in an insertable order?
> - have the load only apply the foreign key constraint at the end of
> each table import?
>
> cheers,
>
> Chris

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800