database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00
Code Activity

Update TODO/FAQ for 7.3 release.

Browse Source
This commit is contained in:
Bruce Momjian
2002-11-16 02:34:22 +00:00
parent 19826a77af
commit cab72f57d5
9 changed files with 33 additions and 142 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
doc/src/FAQ/FAQ_DEV.html
View File

@ -12,7 +12,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1>
<P>Last updated: Sat Nov 2 23:02:16 EST 2002</P>
<P>Last updated: Tue Nov 5 16:52:46 EST 2002</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@ -40,8 +40,8 @@
<A href="#1.7">1.7</A>) What is configure all about?<BR>
<A href="#1.8">1.8</A>) How do I add a new port?<BR>
<A href="#1.9">1.9</A>) Why don't you use threads/raw
devices/async-I/O, &amp;insert your favorite wizz-bang feature
here&amp;?<BR>
devices/async-I/O, &lt;insert your favorite wizz-bang feature
here&gt;?<BR>
<A href="#1.10">1.10</A>) How are RPM's packaged?<BR>
<A href="#1.11">1.11</A>) How are CVS branches handled?<BR>
<A href="#1.12">1.12</A>) Where can I get a copy of the SQL
@ -384,8 +384,8 @@
special files for your OS.</P>
<H3><A name="1.9">1.9</A>) Why don't you use threads/raw
devices/async-I/O, &amp;insert your favorite wizz-bang feature
here&amp;?</H3>
devices/async-I/O, &lt;insert your favorite wizz-bang feature
here&gt;?</H3>
<P>There is always a temptation to use the newest operating system
features as soon as they arrive. We resist that temptation.</P>
@ -393,7 +393,7 @@
<P>First, we support 15+ operating systems, so any new feature has
to be well established before we will consider it. Second, most new
<I>wizz-bang</I> features don't provide <I>dramatic</I>
improvements. Third, the usually have some downside, such as
improvements. Third, they 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
@ -413,10 +413,10 @@
<LI>The backend code would be more complex.</LI>
</UL>
<P>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.</P>
<P>So, we are not ignorant of 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.</P>
<H3><A name="1.10">1.10</A>) How are RPM's packaged?</H3>