| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Subject: | Re: bytea vs. pg_dump |
| Date: | 2009-05-30 13:48:14 |
| Message-ID: | 565C89DC4525DF15B55922B1@teje |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--On Samstag, Mai 30, 2009 00:47:16 +0300 Hannu Krosing
<hannu(at)2ndQuadrant(dot)com> wrote:
> And we can also escape the need to uncompress TOAST'ed fields - just
> markup the compression as another \c at the beginning of data.
Hmm i thought about that, but that seems only to make sense if there is an
easy way to "bypass" compressing the data on restore. Also, it seems to me
that compression/decompression isn't a "real" bottleneck, but that needs to
be confirmed.
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bernd Helmle | 2009-05-30 13:52:20 | Re: bytea vs. pg_dump |
| Previous Message | Bruce Momjian | 2009-05-30 12:11:47 | Re: pg_migrator and an 8.3-compatible tsvector data type |