Re: Configure Postgres From SQL
От | Scott Marlowe |
---|---|
Тема | Re: Configure Postgres From SQL |
Дата | |
Msg-id | AANLkTil_w3B-8MdYwu-LaUXSVd_E80mBnDnb832z600X@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Configure Postgres From SQL (Thom Brown <thombrown@gmail.com>) |
Ответы |
Re: Configure Postgres From SQL
|
Список | pgsql-general |
On Mon, Jul 12, 2010 at 7:57 AM, Thom Brown <thombrown@gmail.com> wrote: > 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? Is there a way to insert the data with these values already set when you first load the db?
В списке pgsql-general по дате отправления: