On 12 July 2010 14:50, Tom Wilcox <hungrytom@gmail.com> 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?
>
> Cheers,
> Tom
>
Hi Tom,
Is it not possible to do these updates in batches, or does it have to be atomic?
(A small note about replying. Please use "reply to all", and on this
mailing list responses should go below.)
Regards
Thom
