PG 7.x was 2000-2003. A full 5 years after MySQL was released.. and 7 years after mSQL.
The performance of mSQL versus pre-Postgres95 has nothing to do with a setting in PG 7.x released years later.
The performance advantage of mSQL was directly related to the stripped down DBMS that was developed to replace Postgres (AGAIN IN 1993) and the incomplete SQL implementation (AGAIN IN 1993)... both tradeoffs that Postgres did not make.
The issue you're referring to is a separate performance issue that did not occur until years later.. after MySQL already won the marketshare race.
Between the start of Postgres in 1986 and PG 7.x, there's about 14 years of history you're forgetting.
Go look back through the -hackers mailing list, probably ~2001-2002. Or maybe just look at the timestamps for when the default changed, in order to get the right time range. :)
The effect of not changing that from the default was PG then pegging the cpu at 100% (moving stuff into and out of the tiny buffer) with terrible performance.
When we raised that default to something reasonable for (at the time) modern systems... our performance magically increased substantially from the perspective of many non-DBAs.
Note - The exact details are in the PG email archives if anyone cares enough to look. :)