|
1 | 1 | <!-- doc/src/sgml/history.sgml -->
|
2 | 2 |
|
3 | 3 | <sect1 id="history">
|
4 |
| - <title>A Brief History of <productname>&productname;</productname></title> |
| 4 | + <title>A Brief History of <productname>PostgreSQL</productname></title> |
5 | 5 |
|
6 | 6 | <indexterm zone="history">
|
7 | 7 | <primary>history</primary>
|
8 |
| - <secondary>of&productname;</secondary> |
| 8 | + <secondary>ofPostgreSQL</secondary> |
9 | 9 | </indexterm>
|
10 | 10 |
|
11 | 11 | <para>
|
12 | 12 | The object-relational database management system now known as
|
13 |
| - <productname>&productname;</productname> is derived from the |
| 13 | + <productname>PostgreSQL</productname> is derived from the |
14 | 14 | <productname>POSTGRES</productname> package written at the
|
15 | 15 | University of California at Berkeley. With over two decades of
|
16 |
| - development behind it, <productname>&productname;</productname> is now |
| 16 | + development behind it, <productname>PostgreSQL</productname> is now |
17 | 17 | the most advanced open-source database available anywhere.
|
18 | 18 | </para>
|
19 | 19 |
|
|
117 | 117 | <acronym>SQL</acronym> (implemented in the server). (Interface
|
118 | 118 | library <link linkend="libpq">libpq</link> was named after PostQUEL.)
|
119 | 119 | Subqueries
|
120 |
| - were not supported until <productname>&productname;</productname> |
| 120 | + were not supported until <productname>PostgreSQL</productname> |
121 | 121 | (see below), but they could be imitated in
|
122 | 122 | <productname>Postgres95</productname> with user-defined
|
123 | 123 | <acronym>SQL</acronym> functions. Aggregate functions were
|
|
184 | 184 | </sect2>
|
185 | 185 |
|
186 | 186 | <sect2>
|
187 |
| - <title><productname>&productname;</productname></title> |
| 187 | + <title><productname>PostgreSQL</productname></title> |
188 | 188 |
|
189 | 189 | <para>
|
190 | 190 | By 1996, it became clear that the name <quote>Postgres95</quote>
|
191 | 191 | would not stand the test of time. We chose a new name,
|
192 |
| - <productname>&productname;</productname>, to reflect the relationship |
| 192 | + <productname>PostgreSQL</productname>, to reflect the relationship |
193 | 193 | between the original <productname>POSTGRES</productname> and the
|
194 | 194 | more recent versions with <acronym>SQL</acronym> capability. At
|
195 | 195 | the same time, we set the version numbering to start at 6.0,
|
|
199 | 199 |
|
200 | 200 | <para>
|
201 | 201 | Many people continue to refer to
|
202 |
| - <productname>&productname;</productname> as <quote>Postgres</quote> |
| 202 | + <productname>PostgreSQL</productname> as <quote>Postgres</quote> |
203 | 203 | (now rarely in all capital letters) because of tradition or because
|
204 | 204 | it is easier to pronounce. This usage is widely accepted as a
|
205 | 205 | nickname or alias.
|
|
209 | 209 | The emphasis during development of
|
210 | 210 | <productname>Postgres95</productname> was on identifying and
|
211 | 211 | understanding existing problems in the server code. With
|
212 |
| - <productname>&productname;</productname>, the emphasis has shifted to |
| 212 | + <productname>PostgreSQL</productname>, the emphasis has shifted to |
213 | 213 | augmenting features and capabilities, although work continues in
|
214 | 214 | all areas.
|
215 | 215 | </para>
|
216 | 216 |
|
217 | 217 | <para>
|
218 |
| - Details about what has happened in <productname>&productname;</> since |
| 218 | + Details about what has happened in <productname>PostgreSQL</> since |
219 | 219 | then can be found in <xref linkend="release">.
|
| 220 | + |
220 | 221 | </para>
|
221 | 222 | </sect2>
|
222 | 223 | </sect1>
|