Merlin, first of all, thanks for your reply!
> hm. where exactly is all this time getting spent? Are you i/o bound?
> cpu bound? Is there any compression going on?
Very good questions. pg_dump -F c compresses per default "at a moderate
level" (manpage), whatever compression level 'moderate' actu
> As discussed extensively in the past [1]
Argh, forgot to add the reference:
[1]: http://archives.postgresql.org/pgsql-hackers/2009-05/msg00192.php
Chris
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpr
Dear list,
As discussed extensively in the past [1], pg_dump tends to be slow for
tables that contain bytea columns with large contents. Starting with
postgres version 8.5 the COPY format of bytea was changed from escape to
hex [1], giving ~50% performance boost.
However, we experience heavy prob
