Re: Wal -long transaction

From: "Ian Harding" <iharding(at)destinydata(dot)com>
To: "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>
Cc: "Greg Stark" <gsstark(at)mit(dot)edu>, pgsql-general(at)postgresql(dot)org
Subject: Re: Wal -long transaction
Date: 2006-03-20 14:31:31
Message-ID: 725602300603200631y10f778cha5fb221a95bd741c@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
> And it's been a while; but I thought transactions like that could
> overflow rollback segments in that other database.
>

ORA-01555: snapshot too old: rollback segment number string with name
"string" too small
Cause: Rollback records needed by a reader for consistent read are
overwritten by other writers.
Action: If in Automatic Undo Management mode, increase the setting of
UNDO_RETENTION. Otherwise, use larger rollback segments.

In 10g you can do

ALTER TABLESPACE UNDO_TS2 RETENTION GUARANTEE;

which will automgically grow the undo tablespace until you run out of
disk space or the transaction ends.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tino Wildenhain 2006-03-20 14:34:30 Re: Updating in multiple tables
Previous Message Luuk Jansen 2006-03-20 14:26:57 Updating in multiple tables