| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ken Winter" <ken(at)sunward(dot)org> |
| Cc: | "PostgreSQL pg-general List" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Problem with pg_dump? |
| Date: | 2008-01-04 20:34:39 |
| Message-ID: | 22299.1199478879@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Ken Winter" <ken(at)sunward(dot)org> writes:
> When I do a pg_dump from an 8.1 database (with options schema-only,
> no-owner, and plain format), the dump file includes the following:
> ALTER SEQUENCE transaction_transaction_id_seq OWNED BY
> "transaction".transaction_id;
Don't use 8.2 pg_dump if you are intending to reload the output into
8.1. In general, pg_dump's output is not promised to be backward
compatible with older server versions.
> (Full disclosure: I am actually getting this error when working through the
> tool "PG Lightning Assistant" (see
> http://www.amsoftwaredesign.com/lightning_admin.php)
There are some "helpful" tools that seem not to be aware that pg_dump
and server versions are closely linked.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-04 20:36:14 | Re: Concurrent modification of plpgsql function body |
| Previous Message | Alex Vinogradovs | 2008-01-04 20:10:38 | Concurrent modification of plpgsql function body |