Re: MultiXactID Wrap-Around

From: paolo romano <paolo(dot)romano(at)yahoo(dot)it>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: MultiXactID Wrap-Around
Date: 2006-07-04 10:41:11
Message-ID: 20060704104111.46656.qmail@web27813.mail.ukl.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Thank you for the feed-back. In fact the risk seems neglibible, but it means that at least I'm not misunderstanding what that code does...

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> ha scritto: paolo romano
writes:
> My doubts now concern MultixactID wrap-around management.
> Afaics, it is possible to spawn multixactids so quickly to have a
> wrap-around and to start overwriting the data stored in the offset
> slru (but analogous considerations apply to the member slru as
> well).

I looked into this when the multixact code was written. There is a
theoretical risk but I think it's entirely theoretical. MXIDs are
unlikely to be consumed faster than XIDs over the long term, and also
can be recycled sooner. So you'd run up against XID wraparound (which
we do defend against) first.

regards, tom lane

Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2006-07-04 13:22:15 pgsql: Remove libpq's PQescapeIdentifier(), not safe from injection
Previous Message Neil Conway 2006-07-04 04:35:49 pgsql: Fix typos in comments.

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas DCP SD 2006-07-04 12:53:54 Re: update/insert, delete/insert efficiency WRT vacuum and
Previous Message Martijn van Oosterhout 2006-07-04 10:14:23 Re: update/insert, delete/insert efficiency WRT vacuum and