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 [EMAIL PROTECTED] ha scritto: paolo romano <[EMAIL PROTECTED]> writes: My doubts now concern MultixactID wrap-around management. Afaics, it is
ops, i did forget to update the e-mail subject, sorry. I am reposting it with an appropriate one. I'm keeping on studying multixact.c and log management, and I hope you can help me, as usual, in clearing my doubts.My
paolo romano wrote:
ops, i did forget to update the e-mail subject, sorry. I am reposting
it with an appropriate one.
Please do NOT create a post on a new subject by using an MUA's reply
mechanism, even if you replace the subject. The MUA will create an
in-reply-to header which will be
paolo romano [EMAIL PROTECTED] 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
