Ordering of pg_dump output
От | Tom Lane |
---|---|
Тема | Ordering of pg_dump output |
Дата | |
Msg-id | 2013.950026486@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] network_ops in 7.0 and pg_dump question (Oleg Bartunov <oleg@sai.msu.su>) |
Ответы |
Re: [HACKERS] Ordering of pg_dump output
Re: [HACKERS] Ordering of pg_dump output Re: [HACKERS] Ordering of pg_dump output |
Список | pgsql-hackers |
Oleg Bartunov <oleg@sai.msu.su> writes: > creation of index works now. But what about pg_dump ? > I still have to edit manually dump file. > look to excerption from dump file: > CREATE TABLE "applicant" ( > "candx" int2 DEFAULT next_applicant() NOT NULL, > "candidate" text, > "candt" int2, > "img" text > ); > This fails because function next_applicant dumps later ! Yeah, it's a known bug. We can't just dump the functions first, though, can we? I'm not sure how carefully function definitions get examined by CREATE FUNCTION. The simplest real solution I've heard so far is to dump database objects in order by OID rather than doing it strictly by type. Is anyone working on this, or does anyone want to? I haven't looked at pg_dump in a while, but I know some other folks have been hacking it recently. regards, tom lane
В списке pgsql-hackers по дате отправления: