This is a discussion on pg_dump object dump-order within the pgsql Admins forums, part of the PostgreSQL category; --> Greetings I'm working with PostgreSQL for quite some time now but only yesterday ran into a specific problem, as ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Greetings I'm working with PostgreSQL for quite some time now but only yesterday ran into a specific problem, as - so far - I have always used customized backup/restore-scripts. PROBLEM: pg_dump seems to dump objects strictly alphabetically, I presume. Hence a table "events" is always dumped _before_ any sequence "events_id_seq" that is already being referenced in the "create table"-statement for table "events". Example CREATE TABLE event ( event_id integer DEFAULT nextval('event_id_seq'::text) NOT NULL, |
| ||||
| KL <zappa_lot@gmx.net> writes: > pg_dump seems to dump objects strictly alphabetically, No, it doesn't ... at least not if you are running 8.0 or later. It looks at dependencies to see what has to be dumped first. (It does prefer alpha order when there's no dependency constraint.) There are various situations where there might not be a dependency entry, but without knowing more about the history of the table and exactly which version you're running, it's hard to speculate about why or what's the best fix. I will point out, however, that the given script does not in fact fail to load in any Postgres version known to me. Maybe you should post your real problem instead of an oversimplified example. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |