Hello, Tom I see your point, but I would like to clarify a few things.
1. Do we consider described measurement method good enough to conclude that sometimes PostgreSQL really spends 3 ms in a spinlock (like a RTT between two Internet hosts in the same city)? If not, what method should be used to approve or disapprove this? 2. If we agree that PostgreSQL does sometimes spend 3 ms in a spinlock do we consider this a problem? 3. If we consider this a problem, what method is considered appropriate to find a real reason of such behaviour so we could fix it? Best regards, Aleksander -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers