>> Yeah, that's definitely a bug but I'm afraid the fix will change the >> TPS number and may break the backward compatibility. Since we have >> lived with bug for years, I hesitate to back port to older stable >> branches... > > My 2¥: I do not think of a good argument to keep wrong tps numbers > once it is known that there are plain wrong, especially as it is not a > behavioral change as such which could block applications or whatever, > just a different number printed at the end of a run. So I would not > bother much with upward compatibility consideration in this case. > > -- > Fabien.
FYI, the bug was there since the thread support was introduced in commit: da0dfb4b1460c3701abc8ed5f516d138dc4654c That was in 9.0, which was released in 2010. Best regards, -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese:http://www.sraoss.co.jp -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
