From fhorch@ecoaccess.org Mon Jun 21 02:04:58 1999 Received: from devel.ecoaccess.org (user-152-16-66-119.adsl.duke.edu [152.16.66.119]) by hub.org (8.9.3/8.9.3) with SMTP id WAA42546 for ; Sun, 20 Jun 1999 22:04:58 -0400 (EDT) (envelope-from fhorch@ecoaccess.org) Received: (qmail 3959 invoked from network); 21 Jun 1999 02:07:29 -0000 Received: from localhost (HELO ecoaccess.org) (127.0.0.1) by localhost with SMTP; 21 Jun 1999 02:07:29 -0000 Sender: fhorch Message-ID: <376D9E60.D169C92@ecoaccess.org> Date: Sun, 20 Jun 1999 22:07:28 -0400 From: Fred Wilson Horch Organization: EcoAccess X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i586) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: pgsql-docs@hub.org Subject: Suggestions for history.sgml file in tutorial Content-Type: multipart/mixed; boundary="------------35327B03A3E92C8448B17936" This is a multi-part message in MIME format. --------------35327B03A3E92C8448B17936 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Some suggestions to clarify the current status of PostgreSQL. Patch attached. Fred Horch --------------35327B03A3E92C8448B17936 Content-Type: text/html; charset=us-ascii; name="history.sgml.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="history.sgml.patch" *** doc/src/sgml/history.sgml Sun Jun 20 21:53:53 1999 --- doc/src/sgml/history.sgml.new Sun Jun 20 21:58:24 1999 *************** *** 1,6 **** --- 1,18 ---- A Short History of <ProductName>Postgres</ProductName> + + The Object-Relational Database Management System now known as + PostgreSQL was originally called + Postgres, and briefly called + Postgres95. With over a decade of + development behind it, PostgreSQL + is the most advanced open-source database available anywhere, + offering multi-version concurrency control and supporting almost + all SQL constructs, including subselects, transactions, and + user-defined types and functions. + + The Berkeley <ProductName>Postgres</ProductName> Project *************** *** 37,44 **** Version 3 appeared in 1991 and added support for multiple storage managers, an improved query executor, and a rewritten rewrite rule system. For the most part, ! releases since then have focused on portability and ! reliability. --- 49,56 ---- Version 3 appeared in 1991 and added support for multiple storage managers, an improved query executor, and a rewritten rewrite rule system. For the most part, ! releases until Postgres95 (see below) ! focused on portability and reliability. *************** *** 70,76 **** ended with Version 4.2. ! <ProductName>Postgres95</ProductName> --- 82,88 ---- ended with Version 4.2. ! <ProductName>Postgres95</ProductName> *************** *** 79,155 **** Andrew Yu and Jolly Chen ! added a SQL language interpreter to Postgres, ! and the code was subsequently released to ! the Web to find its own way in the world. ! Postgres95 was a public-domain, open source descendant ! of this original Berkeley code. ! Postgres95 is a derivative of the last official release ! of Postgres (version 4.2). The code is now completely ! ANSI C and the code size has been trimmed by 25%. There ! are a lot of internal changes that improve performance ! and code maintainability. ! Postgres95 v1.0.x runs about 30-50% ! faster on the Wisconsin Benchmark compared to v4.2. ! Apart from bug fixes, these are the major enhancements: ! The query language Postquel has been replaced with ! SQL (implemented in the server). We do not yet support ! subqueries (which can be imitated with user defined ! SQL functions). Aggregates have been ! re-implemented. We also added support for ``GROUP BY''. ! The libpq interface is still available for C programs. ! In addition to the monitor program, we provide a new ! program (psql) which supports GNU readline. ! We added a new front-end library, libpgtcl, that ! supports Tcl-based clients. A sample shell, ! pgtclsh, provides new Tcl commands to interface tcl programs with the Postgres95 backend. ! The large object interface has been overhauled. We ! kept Inversion large objects as the only mechanism ! for storing large objects. (This is not to be ! confused with the Inversion file system which has been ! removed.) ! The instance-level rule system has been removed. ! Rules are still available as rewrite rules. A short tutorial introducing regular SQL features as ! well as those of ours is distributed with the source ! code. ! GNU make (instead of BSD make) is used for the ! build. Also, Postgres95 can be compiled with an ! unpatched gcc (data alignment of doubles has been ! fixed). --- 91,165 ---- Andrew Yu and Jolly Chen ! added a SQL language interpreter to Postgres. ! Postgres95 was subsequently released to ! the Web to find its own way in the world as a public-domain, ! open source descendant of the original Postgres ! Berkeley code. ! Postgres95 code was completely ! ANSI C and trimmed in size by 25%. Many ! internal changes improved performance and maintainability. ! Postgres95 v1.0.x ran about 30-50% ! faster on the Wisconsin Benchmark compared to ! Postgres v4.2. ! Apart from bug fixes, these were the major enhancements: ! The query language Postquel was replaced with ! SQL (implemented in the server). Subqueries were not supported until PostgreSQL (see below), but they ! could be imitated in Postgres95 with user-defined ! SQL functions. Aggregates were ! re-implemented. Support for ``GROUP BY'' was also added. ! The libpq interface remained available for C programs. ! In addition to the monitor program, a new program ! (psql) was provided for interactive SQL queries ! using GNU readline. ! A new front-end library, libpgtcl, ! supported Tcl-based clients. A sample shell, ! pgtclsh, provided new Tcl commands to interface tcl programs with the Postgres95 backend. ! The large object interface was overhauled. The Inversion large objects were ! the only mechanism for storing large objects. ! (The Inversion file system was removed.) ! The instance-level rule system was removed. ! Rules were still available as rewrite rules. A short tutorial introducing regular SQL features as ! well as those of Postgres95 was ! distributed with the source code. ! GNU make (instead of BSD make) was used ! for the build. Also, Postgres95 could be ! compiled with an unpatched gcc ! (data alignment of doubles was fixed). *************** *** 160,193 **** <ProductName>PostgreSQL</ProductName> ! By 1996, it became clear that the name Postgres95 would not stand ! the test of time. A new name, PostgreSQL, ! was chosen to reflect the ! relationship between original Postgres ! and the more recent ! versions with SQL capability. ! At the same time, the version numbering ! was reset to start at 6.0, ! putting the numbers back into the sequence originally begun by ! the Postgres Project. ! The emphasis on development for the v1.0.x releases of ! Postgres95 ! was on stabilizing the backend code. ! With the v6.x series of PostgreSQL, ! the emphasis has shifted from ! identifying and understanding existing problems in the backend ! to augmenting features and capabilities, although work continues in all areas. ! Major enhancements include: Important backend features, including subselects, defaults, --- 170,206 ---- <ProductName>PostgreSQL</ProductName> ! By 1996, it became clear that the name Postgres95 would ! not stand the test of time. We chose a new name, ! PostgreSQL, to reflect the relationship ! between the original Postgres and the more ! recent versions with SQL capability. At the same ! time, we set the version numbering to start at 6.0, putting the ! numbers back into the sequence originally begun by the ! Postgres Project. ! The emphasis during development of Postgres95 ! was on identifying and understanding existing problems in the backend code. ! With PostgreSQL, ! the emphasis has shifted to augmenting features and capabilities, although work continues in all areas. ! Major enhancements in PostgreSQL include: + + + Table-level locking has been replaced with multi-version concurrency control, + which allows readers to continue reading consistent data during writer activity + and enables hot backups from pg_dump while the database stays available for + queries. + + Important backend features, including subselects, defaults, --------------35327B03A3E92C8448B17936-- From lockhart@alumni.caltech.edu Mon Jun 21 02:49:55 1999 Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA48478 for ; Sun, 20 Jun 1999 22:49:55 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id CAA15472; Mon, 21 Jun 1999 02:50:48 GMT Sender: lockhart@hub.org Message-ID: <376DA888.12C97930@alumni.caltech.edu> Date: Mon, 21 Jun 1999 02:50:48 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Fred Wilson Horch CC: pgsql-docs@hub.org Subject: Re: [DOCS] Suggestions for history.sgml file in tutorial References: <376D9E60.D169C92@ecoaccess.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Some suggestions to clarify the current status of PostgreSQL. Patch > attached. Thanks. They all look good, and while reading it I fixed one or two other places too. > -------------------------------------------------------------- > *** doc/src/sgml/history.sgml Sun Jun 20 21:53:53 1999 --- > doc/src/sgml/history.sgml.new Sun Jun 20 21:58:24 1999 How would you suggest I invoke the patch utility to get this to work? I ended up removing the paths and changing to .sgml.orig and .sgml for the file names. Thanks again for the patch... - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California From maillist@candle.pha.pa.us Mon Jun 21 15:12:25 1999 Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA60658 for ; Mon, 21 Jun 1999 11:12:25 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id LAA16346; Mon, 21 Jun 1999 11:11:49 -0400 (EDT) From: Bruce Momjian Message-Id: <199906211511.LAA16346@candle.pha.pa.us> Subject: Re: [DOCS] Suggestions for history.sgml file in tutorial In-Reply-To: <376D9E60.D169C92@ecoaccess.org> from Fred Wilson Horch at "Jun 20, 1999 10:07:28 pm" To: Fred Wilson Horch Date: Mon, 21 Jun 1999 11:11:49 -0400 (EDT) CC: pgsql-docs@hub.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Patch applied. > Some suggestions to clarify the current status of PostgreSQL. Patch > attached. > > Fred Horch [text/html is unsupported, treating like TEXT/PLAIN] > *** doc/src/sgml/history.sgml Sun Jun 20 21:53:53 1999 > --- doc/src/sgml/history.sgml.new Sun Jun 20 21:58:24 1999 > *************** > *** 1,6 **** > --- 1,18 ---- > > A Short History of <ProductName>Postgres</ProductName> > > + > + The Object-Relational Database Management System now known as > + PostgreSQL was originally called > + Postgres, and briefly called > + Postgres95. With over a decade of > + development behind it, PostgreSQL > + is the most advanced open-source database available anywhere, > + offering multi-version concurrency control and supporting almost > + all SQL constructs, including subselects, transactions, and > + user-defined types and functions. > + > + > > The Berkeley <ProductName>Postgres</ProductName> Project > > *************** > *** 37,44 **** > Version 3 appeared in 1991 and added support for multiple > storage managers, an improved query executor, and a > rewritten rewrite rule system. For the most part, > ! releases since then have focused on portability and > ! reliability. > > > > --- 49,56 ---- > Version 3 appeared in 1991 and added support for multiple > storage managers, an improved query executor, and a > rewritten rewrite rule system. For the most part, > ! releases until Postgres95 (see below) > ! focused on portability and reliability. > > > > *************** > *** 70,76 **** > ended with Version 4.2. > > > ! > > <ProductName>Postgres95</ProductName> > > --- 82,88 ---- > ended with Version 4.2. > > > ! > > <ProductName>Postgres95</ProductName> > > *************** > *** 79,155 **** > Andrew Yu > and > Jolly Chen > ! added a SQL language interpreter to Postgres, > ! and the code was subsequently released to > ! the Web to find its own way in the world. > ! Postgres95 was a public-domain, open source descendant > ! of this original Berkeley code. > > > > ! Postgres95 is a derivative of the last official release > ! of Postgres (version 4.2). The code is now completely > ! ANSI C and the code size has been trimmed by 25%. There > ! are a lot of internal changes that improve performance > ! and code maintainability. > ! Postgres95 v1.0.x runs about 30-50% > ! faster on the Wisconsin Benchmark compared to v4.2. > ! Apart from bug fixes, these are the major enhancements: > > > > > ! The query language Postquel has been replaced with > ! SQL (implemented in the server). We do not yet support > ! subqueries (which can be imitated with user defined > ! SQL functions). Aggregates have been > ! re-implemented. We also added support for ``GROUP BY''. > ! The libpq interface is still available for C > programs. > > > > > ! In addition to the monitor program, we provide a new > ! program (psql) which supports GNU readline. > > > > > ! We added a new front-end library, libpgtcl, that > ! supports Tcl-based clients. A sample shell, > ! pgtclsh, provides new Tcl commands to interface tcl > programs with the Postgres95 backend. > > > > > ! The large object interface has been overhauled. We > ! kept Inversion large objects as the only mechanism > ! for storing large objects. (This is not to be > ! confused with the Inversion file system which has been > ! removed.) > > > > > ! The instance-level rule system has been removed. > ! Rules are still available as rewrite rules. > > > > > A short tutorial introducing regular SQL features as > ! well as those of ours is distributed with the source > ! code. > > > > > ! GNU make (instead of BSD make) is used for the > ! build. Also, Postgres95 can be compiled with an > ! unpatched gcc (data alignment of doubles has been > ! fixed). > > > > --- 91,165 ---- > Andrew Yu > and > Jolly Chen > ! added a SQL language interpreter to Postgres. > ! Postgres95 was subsequently released to > ! the Web to find its own way in the world as a public-domain, > ! open source descendant of the original Postgres > ! Berkeley code. > > > > ! Postgres95 code was completely > ! ANSI C and trimmed in size by 25%. Many > ! internal changes improved performance and maintainability. > ! Postgres95 v1.0.x ran about 30-50% > ! faster on the Wisconsin Benchmark compared to > ! Postgres v4.2. > ! Apart from bug fixes, these were the major enhancements: > > > > > ! The query language Postquel was replaced with > ! SQL (implemented in the server). Subqueries were not supported until PostgreSQL (see below), but they > ! could be imitated in Postgres95 with user-defined > ! SQL functions. Aggregates were > ! re-implemented. Support for ``GROUP BY'' was also added. > ! The libpq interface remained available for C > programs. > > > > > ! In addition to the monitor program, a new program > ! (psql) was provided for interactive SQL queries > ! using GNU readline. > > > > > ! A new front-end library, libpgtcl, > ! supported Tcl-based clients. A sample shell, > ! pgtclsh, provided new Tcl commands to interface tcl > programs with the Postgres95 backend. > > > > > ! The large object interface was overhauled. The Inversion large objects were > ! the only mechanism for storing large objects. > ! (The Inversion file system was removed.) > > > > > ! The instance-level rule system was removed. > ! Rules were still available as rewrite rules. > > > > > A short tutorial introducing regular SQL features as > ! well as those of Postgres95 was > ! distributed with the source code. > > > > > ! GNU make (instead of BSD make) was used > ! for the build. Also, Postgres95 could be > ! compiled with an unpatched gcc > ! (data alignment of doubles was fixed). > > > > *************** > *** 160,193 **** > <ProductName>PostgreSQL</ProductName> > > > ! By 1996, it became clear that the name Postgres95 would not stand > ! the test of time. A new name, PostgreSQL, > ! was chosen to reflect the > ! relationship between original Postgres > ! and the more recent > ! versions with SQL capability. > ! At the same time, the version numbering > ! was reset to start at 6.0, > ! putting the numbers back into the sequence originally begun by > ! the Postgres Project. > > > > ! The emphasis on development for the v1.0.x releases of > ! Postgres95 > ! was on stabilizing the backend code. > ! With the v6.x series of PostgreSQL, > ! the emphasis has shifted from > ! identifying and understanding existing problems in the backend > ! to augmenting features and capabilities, although > work continues in all areas. > > > > ! Major enhancements include: > > > > > > Important backend features, including subselects, defaults, > --- 170,206 ---- > <ProductName>PostgreSQL</ProductName> > > > ! By 1996, it became clear that the name Postgres95 would > ! not stand the test of time. We chose a new name, > ! PostgreSQL, to reflect the relationship > ! between the original Postgres and the more > ! recent versions with SQL capability. At the same > ! time, we set the version numbering to start at 6.0, putting the > ! numbers back into the sequence originally begun by the > ! Postgres Project. > > > > ! The emphasis during development of Postgres95 > ! was on identifying and understanding existing problems in the backend code. > ! With PostgreSQL, > ! the emphasis has shifted to augmenting features and capabilities, although > work continues in all areas. > > > > ! Major enhancements in PostgreSQL include: > > > > + > + > + Table-level locking has been replaced with multi-version concurrency control, > + which allows readers to continue reading consistent data during writer activity > + and enables hot backups from pg_dump while the database stays available for > + queries. > + > + > > > Important backend features, including subselects, defaults, -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 From maillist@candle.pha.pa.us Mon Jun 21 15:26:51 1999 Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA63399 for ; Mon, 21 Jun 1999 11:26:51 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id LAA16739; Mon, 21 Jun 1999 11:24:33 -0400 (EDT) From: Bruce Momjian Message-Id: <199906211524.LAA16739@candle.pha.pa.us> Subject: Re: [DOCS] Suggestions for history.sgml file in tutorial In-Reply-To: <376DA888.12C97930@alumni.caltech.edu> from Thomas Lockhart at "Jun 21, 1999 02:50:48 am" To: Thomas Lockhart Date: Mon, 21 Jun 1999 11:24:33 -0400 (EDT) CC: Fred Wilson Horch , pgsql-docs@hub.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > > Some suggestions to clarify the current status of PostgreSQL. Patch > > attached. > > Thanks. They all look good, and while reading it I fixed one or two > other places too. > > > -------------------------------------------------------------- > > *** doc/src/sgml/history.sgml Sun Jun 20 21:53:53 1999 --- > > doc/src/sgml/history.sgml.new Sun Jun 20 21:58:24 1999 > > How would you suggest I invoke the patch utility to get this to work? > I ended up removing the paths and changing to .sgml.orig and .sgml for > the file names. > > Thanks again for the patch... Oops, was I not supposed to apply these. Thomas, I thought you were done with private copies of these files, right? -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 From lockhart@alumni.caltech.edu Tue Jun 22 06:07:46 1999 Received: from localhost (IDENT:root@hectic-2.jpl.nasa.gov [128.149.68.204]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA35547 for ; Tue, 22 Jun 1999 02:07:46 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id GAA19719; Tue, 22 Jun 1999 06:08:58 GMT Sender: lockhart@hub.org Message-ID: <376F287A.8133D30F@alumni.caltech.edu> Date: Tue, 22 Jun 1999 06:08:58 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Momjian CC: Fred Wilson Horch , pgsql-docs@hub.org Subject: Re: [DOCS] Suggestions for history.sgml file in tutorial References: <199906211524.LAA16739@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Oops, was I not supposed to apply these. Thomas, I thought you were > done with private copies of these files, right? Well, with the docs I read and check the patches, and sometimes will take the opportunity to make additional changes or to fix things nearby. Just like you do with the source code patches. In this case I can just slap my version on top of your changes, since with the docs files I usually don't bother shipping diffs to hub.org. Tell ya what, let me handle the sgml patching, and everything else is yours ;) - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California