Re: AW: Modified pg_dump & new pg_restore need testing...
От | Tom Lane |
---|---|
Тема | Re: AW: Modified pg_dump & new pg_restore need testing... |
Дата | |
Msg-id | 19337.962636263@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | AW: Modified pg_dump & new pg_restore need testing... (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>) |
Список | pgsql-hackers |
Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at> writes: > Imho the default should be text for anything except data. The data > should imho be in a format similar to a binary cursor. I say similar, > because this format should probably be converted to a network byte > order, so you can restore on another hardware. Imho calling type > output and input functions during backup/restore is a substantial > overhead that would best be avoided. I think this would be an extremely *bad* idea. One of the principal functions of pg_dump is to provide a portable representation of data; that is, portable across machines and across Postgres versions (where the internal representation of data may change!). Not only should binary data representation not be the default, IMHO we shouldn't offer it as an option either. Otherwise dbadmins will promptly shoot themselves in the foot with it. Do you want to field the support calls saying "help, I already blew away my 7.n installation but 7.n+1 won't read my pg_dump backup"? regards, tom lane
В списке pgsql-hackers по дате отправления: