| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: bytea vs. pg_dump |
| Date: | 2009-05-11 09:15:32 |
| Message-ID: | 01C1F6AB0CFF8A52B30DF0F3@teje |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
--On Mittwoch, Mai 06, 2009 19:04:21 -0400 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
wrote:
> So I'm now persuaded that a better textual representation for bytea
> should indeed make things noticeably better here. It would be
> useful though to cross-check this thought by profiling a case that
> dumps a comparable volume of text data that contains no backslashes...
I'm going to try to create a profile with a converted text representation
of the data.
--
Thanks
Bernd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hans-Juergen Schoenig | 2009-05-11 09:18:43 | Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5 |
| Previous Message | Greg Stark | 2009-05-11 08:29:46 | Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5 |