From 659df79e45471025ff4052eaab3cb693fbfc694b Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Sun, 3 Nov 2002 04:02:32 +0000 Subject: Update FAQ_DEV. --- doc/src/FAQ/FAQ_DEV.html | 31 ++++++++++++++++++++++++++----- 1 file changed, 26 insertions(+), 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html index 6b2e1363f21..24baab3eb33 100644 --- a/doc/src/FAQ/FAQ_DEV.html +++ b/doc/src/FAQ/FAQ_DEV.html @@ -12,7 +12,7 @@

Developer's Frequently Asked Questions (FAQ) for PostgreSQL

-

Last updated: Tue Aug 13 16:41:02 EDT 2002

+

Last updated: Sat Nov 2 23:02:16 EST 2002

Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -39,7 +39,9 @@ 1.6) What books are good for developers?
1.7) What is configure all about?
1.8) How do I add a new port?
- 1.9) Why don't we use threads in the backend?
+ 1.9) Why don't you use threads/raw + devices/async-I/O, &insert your favorite wizz-bang feature + here&?
1.10) How are RPM's packaged?
1.11) How are CVS branches handled?
1.12) Where can I get a copy of the SQL @@ -381,10 +383,24 @@ handling. There is a backend/port directory if you need special files for your OS.

-

1.9) Why don't we use threads in the - backend?

+

1.9) Why don't you use threads/raw + devices/async-I/O, &insert your favorite wizz-bang feature + here&?

-

There are several reasons threads are not used:

+

There is always a temptation to use the newest operating system + features as soon as they arrive. We resist that temptation.

+ +

First, we support 15+ operating systems, so any new feature has + to be well established before we will consider it. Second, most new + wizz-bang features don't provide dramatic + improvements. Third, the usually have some downside, such as + decreased reliability or additional code required. Therefore, we + don't rush to use new features but rather wait for the feature to be + established, then ask for testing to show that a measurable + improvement is possible.

+ +

As an example, threads are not currently used in the backend code + because:

+

So, we are not "asleep at the switch" as they say with regard to + new features, it is just that we are cautious about their + adoption. The TODO list often contains links to discussions + showing our reasoning in these areas.

+

1.10) How are RPM's packaged?

This was written by Lamar Owen:

-- cgit v1.2.3