>>>>> "TG" == Tom Glover <firstname.lastname@example.org> writes:
TG> I'm not so sure that its plugged. One of my larger lists got its
TG> subscriber list zeroed last week following some race conditions.
Could you describe these race conditions? When testing 1.94.1 before its
release, I ran it through the torturous task of processing 10000
simultaneous subscriptions _and_ 10000 simultaneous unsubscriptions on a
list that already had 20000 members. This drove load averages through the
roof (100+) and took a really long time to get through everything but at
the end the list was essentially as expected. There were a few lock
timeouts and such but the list was not zeroed.
Of course that's not a scientific test and it only proves that the locking
for subscriptions and unsubscriptions is at least pretty good on my
platform. If there really is a locking bug I'd really like to find the
root of it.