Re: [HACKERS] pg_dump/restore to convert BLOBs to LZTEXT (optional!)
От | Philip Warner |
---|---|
Тема | Re: [HACKERS] pg_dump/restore to convert BLOBs to LZTEXT (optional!) |
Дата | |
Msg-id | 3.0.5.32.20000804112928.026df4f0@mail.rhyme.com.au обсуждение исходный текст |
Ответ на | Re: [HACKERS] pg_dump/restore to convert BLOBs to LZTEXT (optional!) (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-general |
At 21:10 3/08/00 -0400, Tom Lane wrote: >As well as break the semantics: if you have a multiply-referenced BLOB >then you can update it through any reference and the changes are visible >through all the references. Not so after you convert the data into >non-BLOB values. That's what I meant. People *shouldn't* expect BLOB fields to be updated in more than one table, but the implementation currently allow it (since BLOBs are not implemented as fields). >I don't see that pg_dump can help meaningfully, >and I'd just as soon resist feature bloat in pg_dump. Fine. Thinking about it, even *if* it was implemented as a utility, I suspect (for the reasons you outlined), conversion would be a multi-step process. And a more useful utility would be one that converted an existing database, rather than trying to everything in the 'restore'... Forget I even mentioned it. ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.C.N. 008 659 498) | /(@) ______---_ Tel: (+61) 0500 83 82 81 | _________ \ Fax: (+61) 0500 83 82 82 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/
В списке pgsql-general по дате отправления: