1212< H1 > Developer's Frequently Asked Questions (FAQ) for
1313 PostgreSQL</ H1 >
1414
15- < P > Last updated: Tue Nov 5 16:49:16 EST 2002</ P >
15+ < P > Last updated: Tue Nov 5 16:52:46 EST 2002</ P >
1616
1717< P > Current maintainer: Bruce Momjian (< A href =
1818 "mailto:pgman@candle.pha.pa.us "> pgman@candle.pha.pa.us</ A > )< BR >
@@ -393,7 +393,7 @@ <H3><A name="1.9">1.9</A>) Why don't you use threads/raw
393393< P > First, we support 15+ operating systems, so any new feature has
394394 to be well established before we will consider it. Second, most new
395395< I > wizz-bang</ I > features don't provide< I > dramatic</ I >
396- improvements. Third,the usually have some downside, such as
396+ improvements. Third,they usually have some downside, such as
397397 decreased reliability or additional code required. Therefore, we
398398 don't rush to use new features but rather wait for the feature to be
399399 established, then ask for testing to show that a measurable
@@ -413,10 +413,10 @@ <H3><A name="1.9">1.9</A>) Why don't you use threads/raw
413413< LI > The backend code would be more complex.</ LI >
414414</ UL >
415415
416- < P > So, we are not"asleep at the switch" as they say with regard to
417- new features, it is just that we are cautious about their
418- adoption. The TODO list often contains links to discussions
419- showing our reasoning in these areas.</ P >
416+ < P > So, we are notignorant of new features. It is just that
417+ we are cautious about their adoption. The TODO list often
418+ contains links to discussionsshowing our reasoning in
419+ these areas.</ P >
420420
421421< H3 > < A name ="1.10 "> 1.10</ A > ) How are RPM's packaged?</ H3 >
422422