| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | paolo romano <paolo(dot)romano(at)yahoo(dot)it> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: MultiXactID Wrap-Around |
| Date: | 2006-07-03 15:21:56 |
| Message-ID: | 3276.1151940116@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
paolo romano <paolo(dot)romano(at)yahoo(dot)it> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-03 16:43:14 | pgsql: Fix broken markup. |
| Previous Message | Andrew Dunstan | 2006-07-03 13:58:06 | Re: MultiXactID Wrap-Around |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2006-07-03 15:24:49 | Re: CVS mirror, was Re: [PATCHES] ADD/DROPS INHERIT (actually INHERIT |
| Previous Message | Andrew Dunstan | 2006-07-03 15:08:18 | CVS mirror, was Re: [PATCHES] ADD/DROPS INHERIT (actually INHERIT / NO INHERIT) |