Search Postgresql Archives

Re: Wal -long transaction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Martijn van Oosterhout <kleptog@xxxxxxxxx> writes:
> On Mon, Mar 13, 2006 at 03:59:33PM +0100, Agnes Bocchino wrote:
>> (I have tried to make the test but without success for finding a long
>> transaction)

> AIUI it just keeps creating more segments. i.e. checkpoint_segment is
> not a hard limit. It's just the number it keeps around and recycles
> rather than continually creating and deleteing files.

More to the point, having a long transaction has nothing to do with this
(we are not Oracle!).  The only thing that determines the amount of WAL
space needed is the time between checkpoints.  You can have a
transaction that stays open for many checkpoints without causing WAL to
bloat.

Of course, there's no free lunch --- the price we pay for escaping
rollback-segment-overflow is table bloat if you don't vacuum often
enough.

			regards, tom lane


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux