I could perform the settings manually (set config, restart svr, execute
script, come back 2 days later, reset config, restart svr, execute more
script,...), but that sort of defeats the point. My aim to have the
simplest, automatic setup possible. Preferably completely contained
within PostgreSQL so that all is need is a dump of the DB for a complete
backup...
On 12/07/2010 19:26, Scott Marlowe wrote:
On Mon, Jul 12, 2010 at 7:57 AM, Thom Brown<thombrown@xxxxxxxxx> wrote:
On 12 July 2010 14:50, Tom Wilcox<hungrytom@xxxxxxxxx> wrote:
Hi Thom,
I am performing update statements that are applied to a single table that is
about 96GB in size. These updates are grouped together in a single
transaction. This transaction runs until the machine runs out of disk space.
What I am trying to achieve is for postgresql to complete this updating
transaction without running out of memory. I assume that this is happening
because for a Rollback to be possible, postgres must at least keep track of
the previous values/changes whilst the transaction is not complete and
committed. I figured this would be the most likely cause for us to run out
of disk space and therefore I would like to reconfigure postgresql not to
hold onto previous copies somehow.
Any suggestions?
Is there a way to insert the data with these values already set when
you first load the db?
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
