Re: bytea vs. pg_dump
| От | Hannu Krosing |
|---|---|
| Тема | Re: bytea vs. pg_dump |
| Дата | |
| Msg-id | 1243633400.5399.31.camel@huvostro обсуждение исходный текст |
| Ответ на | Re: bytea vs. pg_dump (Peter Eisentraut <peter_e@gmx.net>) |
| Список | pgsql-hackers |
On Fri, 2009-05-29 at 11:06 +0300, Peter Eisentraut wrote: > On Friday 29 May 2009 04:26:35 Bruce Momjian wrote: > > Added to TODO: > > |Improve bytea COPY format > > > > * http://archives.postgresql.org/pgsql-hackers/2009-05/msg00192.php > > Btw., I have started to write some code for that. why not copy bytea always in base64 encoded or similar format - this will both save at least 2x the space on average random bytea data _and_ is probably faster, as it can be more easily done by table lookups in bigger chunks an alternative is to just escape minimal amount of characters, probably just \0 , \n and \\ -- Hannu Krosing http://www.2ndQuadrant.com PostgreSQL Scalability and Availability Services, Consulting and Training
В списке pgsql-hackers по дате отправления: