Hi Micheal,, > I have just read the patch, and hardcoding the array position for a > socket event to 0 assumes that the socket event will be *always* the > first one in the list. but that cannot be true all the time, any code > that does not register the socket event as the first one in the list > will likely break.
I think your point is very valid and even i had similar thought in my mind when implementing it but as i mentioned upthread that's how it is being used in the current code base. Please check a function call to ModifyWaitEvent() in secure_read(). -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
