mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update FAQ_DEV.

Browse Source
This commit is contained in:
Bruce Momjian 2002-11-05 21:53:24 +00:00
parent d3d54d4b41
commit 6ac7538337
2 changed files with 11 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/FAQ_DEV
View File

@ -1,7 +1,7 @@
Developer's Frequently Asked Questions (FAQ) for PostgreSQL Developer's Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Tue Nov 5 16:49:16 EST 2002 Last updated: Tue Nov 5 16:52:46 EST 2002
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@ -325,7 +325,7 @@
First, we support 15+ operating systems, so any new feature has to be First, we support 15+ operating systems, so any new feature has to be
well established before we will consider it. Second, most new well established before we will consider it. Second, most new
wizz-bang features don't provide dramatic improvements. Third, the wizz-bang features don't provide dramatic improvements. Third, they
usually have some downside, such as decreased reliability or usually have some downside, such as decreased reliability or
additional code required. Therefore, we don't rush to use new features additional code required. Therefore, we don't rush to use new features
but rather wait for the feature to be established, then ask for but rather wait for the feature to be established, then ask for
@ -339,10 +339,9 @@
remaining backend startup time. remaining backend startup time.
* The backend code would be more complex. * The backend code would be more complex.
So, we are not "asleep at the switch" as they say with regard to new So, we are not ignorant of new features. It is just that we are
features, it is just that we are cautious about their adoption. The cautious about their adoption. The TODO list often contains links to
TODO list often contains links to discussions showing our reasoning in discussions showing our reasoning in these areas.
these areas.
1.10) How are RPM's packaged? 1.10) How are RPM's packaged?

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

@ -12,7 +12,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for <H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1> PostgreSQL</H1>
<P>Last updated: Tue Nov 5 16:49:16 EST 2002</P> <P>Last updated: Tue Nov 5 16:52:46 EST 2002</P>
<P>Current maintainer: Bruce Momjian (<A href= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
@ -393,7 +393,7 @@
<P>First, we support 15+ operating systems, so any new feature has <P>First, we support 15+ operating systems, so any new feature has
to be well established before we will consider it. Second, most new to be well established before we will consider it. Second, most new
<I>wizz-bang</I> features don't provide <I>dramatic</I> <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 decreased reliability or additional code required. Therefore, we
don't rush to use new features but rather wait for the feature to be 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 established, then ask for testing to show that a measurable
@ -413,10 +413,10 @@
<LI>The backend code would be more complex.</LI> <LI>The backend code would be more complex.</LI>
</UL> </UL>
<P>So, we are not "asleep at the switch" as they say with regard to <P>So, we are not ignorant of new features. It is just that
new features, it is just that we are cautious about their we are cautious about their adoption. The TODO list often
adoption. The TODO list often contains links to discussions contains links to discussions showing our reasoning in
showing our reasoning in these areas.</P> these areas.</P>
<H3><A name="1.10">1.10</A>) How are RPM's packaged?</H3> <H3><A name="1.10">1.10</A>) How are RPM's packaged?</H3>