Sebastien Boisvert <[email protected]> writes:
> ----- Original Message ----
>> From: Tom Lane <[email protected]>
>>> [ COPY fails to dump a 138MB bytea column ]
>> I wonder whether you are doing anything that exacerbates
>> the memory requirement, for instance by forcing an encoding conversion to
>> something other than the database's server_encoding.
> Our backups are done with the "-F c" (in addition to the normal
> user/host/port options). As far as I know that shouldn't be
> triggering any type conversions (which is UTF8 all-around).
No, that wouldn't do it. I'm thinking about forcing client_encoding to
be different from the database encoding, via pg_dump's -E switch, or
indirectly via PGCLIENTENCODING or PGOPTIONS or a user-specific
client_encoding setting (there are some other ways to set
client_encoding too). You could double check that by seeing what
client_encoding is specified in pg_dump's output.
regards, tom lane
--
Sent via pgsql-general mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
