At 18:56 18/08/2008, André Knappstein wrote:

>Hello Andi,
>
>> Oldest transaction 27036789
>> Oldest active 27036790
>> Oldest snapshot 27036790
>> Next transaction 27036791
>
>> Creation date Jan 18, 2007 18:11:29
>> Attributes force write
>
>
>Your database is running for 18+ months and has piled up 27 million
>transaction corpses without ever having been backed-up/restored. While
>I can not say for certain that this will help much in your actual
>situation, it is surely worth trying to do a backup/restore.
>
>Ann Harrison has - not too long ago - in this forum described how long
>gone transactions still hold space in the database.

...which you didn't quite understand, methinks...while it's true that they have not restored their database for 20 months, that does not cause "27 million transactions to pile up". Transactions don't "pile up" and their system isn't "piling up" anything. Long-running transactions cause obsolete record versions to "pile up" (garbage, that is). But their application code is taking very good care of transactions, in fact these statistics are as close to "perfect" as I have ever seen in a production database.

./heLen