Transaction ID wraparound, Oracle style

From: Igor Polishchuk <igor(at)powerreviews(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Transaction ID wraparound, Oracle style
Date: 2012-01-18 18:21:25
Message-ID: CB3C4DA5.1711D%igor@powerreviews.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Here is an article on a recently discovered Oracle flaw, which allows SCN to
reach its limit.
http://www.computerworld.com/s/article/9223506/Fundamental_Oracle_flaw_revea
led?taxonomyId=18&pageNumber=1

Please don't beat me for posting a link for an Oracle related article.
If you despise a very notion of mentioning Oracle, please just don't read
the post.
This article may be interesting to any RDBMS professional, no mater what db
flavor he/she is working with.
Also, this story may be a lesson for the Postgresql community on how not do
things. I'm not a developer, but it seems that having synchronized
transaction id between let say streaming-replicated databases would give
some advantages if done properly.
Regards
Igor Polishchuk

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2012-01-18 19:15:59 Re: Transaction ID wraparound, Oracle style
Previous Message Tom Lane 2012-01-18 18:08:21 Re: scenario with a slow query