Re: Dump Version
От | Philip Warner |
---|---|
Тема | Re: Dump Version |
Дата | |
Msg-id | 6.1.1.1.0.20040813230558.08d32e10@203.8.195.10 обсуждение исходный текст |
Ответ на | Re: Dump Version (strk <strk@keybit.net>) |
Ответы |
Re: Dump Version
|
Список | pgsql-hackers |
At 10:30 PM 13/08/2004, strk wrote: > >From PG73: > 552; 2663984 CAST bytea (public.wkb) > >From PG74: > 547; 1915318 CAST CAST (public.wkb AS bytea) > >Since these two dumps have same file format version I asked.. The file format (unfortunately for you) does not define the format of the contents of the TOC entries. It may be messy, but you could use your source sql file to create an empty database in the same PG version, then do: pg_dump -Fc tempdatabase | pg_restore -l to get a compatible list. But you'll still have mismatched OIDs, and a temp database to create/cleanup. I can't see another way that won't require constant updates & tweaking into the future. ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.B.N. 75 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 03 5330 3172 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp.mit.edu:11371 |/
В списке pgsql-hackers по дате отправления: