Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit659df79

Browse files
committed
Update FAQ_DEV.
1 parent24135fb commit659df79

File tree

2 files changed

+49
-9
lines changed

2 files changed

+49
-9
lines changed

‎doc/FAQ_DEV

Lines changed: 23 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated:Tue Aug 13 16:41:02 EDT 2002
4+
Last updated:Sat Nov 2 23:02:16 EST 2002
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

@@ -19,7 +19,8 @@
1919
1.6) What books are good for developers?
2020
1.7) What is configure all about?
2121
1.8) How do I add a new port?
22-
1.9) Why don't we use threads in the backend?
22+
1.9) Why don't you use threads/raw devices/async-I/O, &insert your
23+
favorite wizz-bang feature here&?
2324
1.10) How are RPM's packaged?
2425
1.11) How are CVS branches handled?
2526
1.12) Where can I get a copy of the SQL standards?
@@ -316,15 +317,33 @@
316317
src/makefiles directory for port-specific Makefile handling. There is
317318
a backend/port directory if you need special files for your OS.
318319

319-
1.9) Why don't we use threads in the backend?
320+
1.9) Why don't you use threads/raw devices/async-I/O, &insert your favorite
321+
wizz-bang feature here&?
320322

321-
There are several reasons threads are not used:
323+
There is always a temptation to use the newest operating system
324+
features as soon as they arrive. We resist that temptation.
325+
326+
First, we support 15+ operating systems, so any new feature has to be
327+
well established before we will consider it. Second, most new
328+
wizz-bang features don't provide dramatic improvements. Third, the
329+
usually have some downside, such as decreased reliability or
330+
additional code required. Therefore, we don't rush to use new features
331+
but rather wait for the feature to be established, then ask for
332+
testing to show that a measurable improvement is possible.
333+
334+
As an example, threads are not currently used in the backend code
335+
because:
322336
* Historically, threads were unsupported and buggy.
323337
* An error in one backend can corrupt other backends.
324338
* Speed improvements using threads are small compared to the
325339
remaining backend startup time.
326340
* The backend code would be more complex.
327341

342+
So, we are not "asleep at the switch" as they say with regard to new
343+
features, it is just that we are cautious about their adoption. The
344+
TODO list often contains links to discussions showing our reasoning in
345+
these areas.
346+
328347
1.10) How are RPM's packaged?
329348

330349
This was written by Lamar Owen:

‎doc/src/FAQ/FAQ_DEV.html

Lines changed: 26 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@
1212
<H1>Developer's Frequently Asked Questions (FAQ) for
1313
PostgreSQL</H1>
1414

15-
<P>Last updated:Tue Aug 13 16:41:02 EDT 2002</P>
15+
<P>Last updated:Sat Nov 2 23:02:16 EST 2002</P>
1616

1717
<P>Current maintainer: Bruce Momjian (<Ahref=
1818
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@@ -39,7 +39,9 @@ <H2>General Questions</H2>
3939
<Ahref="#1.6">1.6</A>) What books are good for developers?<BR>
4040
<Ahref="#1.7">1.7</A>) What is configure all about?<BR>
4141
<Ahref="#1.8">1.8</A>) How do I add a new port?<BR>
42-
<Ahref="#1.9">1.9</A>) Why don't we use threads in the backend?<BR>
42+
<Ahref="#1.9">1.9</A>) Why don't you use threads/raw
43+
devices/async-I/O, &amp;insert your favorite wizz-bang feature
44+
here&amp;?<BR>
4345
<Ahref="#1.10">1.10</A>) How are RPM's packaged?<BR>
4446
<Ahref="#1.11">1.11</A>) How are CVS branches handled?<BR>
4547
<Ahref="#1.12">1.12</A>) Where can I get a copy of the SQL
@@ -381,10 +383,24 @@ <H3><A name="1.8">1.8</A>) How do I add a new port?</H3>
381383
handling. There is a<I>backend/port</I> directory if you need
382384
special files for your OS.</P>
383385

384-
<H3><Aname="1.9">1.9</A>) Why don't we use threads in the
385-
backend?</H3>
386+
<H3><Aname="1.9">1.9</A>) Why don't you use threads/raw
387+
devices/async-I/O, &amp;insert your favorite wizz-bang feature
388+
here&amp;?</H3>
386389

387-
<P>There are several reasons threads are not used:</P>
390+
<P>There is always a temptation to use the newest operating system
391+
features as soon as they arrive. We resist that temptation.</P>
392+
393+
<P>First, we support 15+ operating systems, so any new feature has
394+
to be well established before we will consider it. Second, most new
395+
<I>wizz-bang</I> features don't provide<I>dramatic</I>
396+
improvements. Third, the usually have some downside, such as
397+
decreased reliability or additional code required. Therefore, we
398+
don't rush to use new features but rather wait for the feature to be
399+
established, then ask for testing to show that a measurable
400+
improvement is possible.</P>
401+
402+
<P>As an example, threads are not currently used in the backend code
403+
because:</P>
388404

389405
<UL>
390406
<LI>Historically, threads were unsupported and buggy.</LI>
@@ -397,6 +413,11 @@ <H3><A name="1.9">1.9</A>) Why don't we use threads in the
397413
<LI>The backend code would be more complex.</LI>
398414
</UL>
399415

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>
420+
400421
<H3><Aname="1.10">1.10</A>) How are RPM's packaged?</H3>
401422

402423
<P>This was written by Lamar Owen:</P>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp