From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Thom Brown <thombrown(at)gmail(dot)com> |
Cc: | Tom Wilcox <hungrytom(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Configure Postgres From SQL |
Date: | 2010-07-12 18:26:01 |
Message-ID: | AANLkTil_w3B-8MdYwu-LaUXSVd_E80mBnDnb832z600X@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Jul 12, 2010 at 7:57 AM, Thom Brown <thombrown(at)gmail(dot)com> wrote:
> On 12 July 2010 14:50, Tom Wilcox <hungrytom(at)gmail(dot)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?
Is there a way to insert the data with these values already set when
you first load the db?
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2010-07-12 18:54:53 | Re: PG_DUMP very slow because of STDOUT ?? |
Previous Message | Brad Nicholson | 2010-07-12 18:04:58 | Re: Configure Postgres From SQL |