Skip site navigation (1) Skip section navigation (2)

Re: Problems backing up

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sebastien Boisvert <sebastienboisvert(at)yahoo(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problems backing up
Date: 2010-01-31 19:02:38
Message-ID: 14282.1264964558@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-general
Sebastien Boisvert <sebastienboisvert(at)yahoo(dot)com> writes:
> [ COPY fails to dump a 138MB bytea column ]

If you can't switch to a 64-bit build of Postgres, you might need to
think about converting those byteas to large objects.  It's expected for
COPY to require memory space equal to several times the width of the row
it's trying to dump, because it has to have multiple copies of the row
data in order to do format conversion.  In this case the required space
seems to be going well past 1GB, so 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.

But having said that, it seems a bit odd that it is failing at what
seems to be only around 2GB of memory demand.  Even in a 32-bit build
I'd expect there to be enough address space for that, especially in
view of your very small (arguably too small) shared_buffers setting.
Are you sure the postmaster is really being started with 'unlimited'
ulimits?

			regards, tom lane

In response to

Responses

pgsql-general by date

Next:From: Mads Lie JensenDate: 2010-01-31 20:01:01
Subject: Which version will this run on?
Previous:From: Magnus HaganderDate: 2010-01-31 17:59:52
Subject: Re: Versions RSS page is missing version(s)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group