Suggestions for history.sgml file in tutorial

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

*** 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?

This works for me:

1. save patch file to doc/src/sgml/history.sgml.patch
2. cd doc/src/sgml
3. patch < history.sgml.patch

On my system, this patches the history.sgml file. What happens when you
try it?

I'm using

$ patch --version
patch 2.5
Copyright 1988 Larry Wall
Copyright 1997 Free Software Foundation, Inc.

This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of this program
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING.

written by Larry Wall with lots o' patches by Paul Eggert

$ uname -a
Linux devel.ecoaccess.org 2.0.36 #1 Thu Mar 4 15:18:55 EST 1999 i586
unknown

Let me know if you'd rather I save the original file to .orig rather
than create a .new file. Either way works for me.

--Fred Horch

P.S. Actually, now that I've got font-lock working with psgml mode, I
like keeping the .sgml extension on both files, so I call the new one
.new.sgml. I can cp the orig file to .orig.sgml just as easily.

The one thing about renaming the original files to .orig is that I get
confused when doing cvs updates. By keeping all of my changes in .new
files, it's clearer to me which of my changes made it into the official
Postgres repository. But again, I'll do whatever makes it easier for
you.

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 ----
<Sect1>
<Title>A Short History of <ProductName>Postgres</ProductName></Title>

+ <Para>
+ The Object-Relational Database Management System now known as 
+ <ProductName>PostgreSQL</ProductName> was originally called
+ <ProductName>Postgres</ProductName>, and briefly called
+ <ProductName>Postgres95</ProductName>.  With over a decade of
+ development behind it, <ProductName>PostgreSQL</ProductName> 
+ 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.
+ </Para>
+ 
<Sect2>
<Title>The Berkeley <ProductName>Postgres</ProductName> Project</Title>

***************
*** 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.
</Para>

<Para>
--- 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 <ProductName>Postgres95</ProductName> (see below)
!      focused on portability and reliability.
</Para>

<Para>
***************
*** 70,76 ****
ended with Version 4.2.
</Para>
</Sect2>
!
<Sect2>
<Title><ProductName>Postgres95</ProductName></Title>

--- 82,88 ----
ended with Version 4.2.
</Para>
</Sect2>
! 
<Sect2>
<Title><ProductName>Postgres95</ProductName></Title>

***************
*** 79,155 ****
<ULink url="mailto:ayu@informix.com">Andrew Yu</ULink>
and
<ULink url="http://http.cs.berkeley.edu/~jolly/&quot;&gt;Jolly Chen</ULink>
! added a SQL language interpreter to <ProductName>Postgres</ProductName>,
! and the code was subsequently released to
! the Web to find its own way in the world.
! <ProductName>Postgres95</ProductName> was a public-domain, open source descendant
! of this original Berkeley code.
</Para>

<Para>
! <ProductName>Postgres95</ProductName> is a derivative of the last official release
! of <ProductName>Postgres</ProductName> (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.
! <ProductName>Postgres95</ProductName> 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:

<ItemizedList>
<ListItem>
<Para>
!       	The query language <ProductName>Postquel</ProductName> has been replaced with
!         	<Acronym>SQL</Acronym> (implemented in the server). We do  not yet support
!         	subqueries  (which can be imitated with user defined
!         	<Acronym>SQL</Acronym> functions). Aggregates  have  been
!         	re-implemented.  We also added support for ``GROUP BY''.
!         	The <FileName>libpq</FileName> interface is still available  for  <Acronym>C</Acronym>  
programs.
</Para>
</ListItem>
<ListItem>
<Para>
!       	In addition to the monitor program, we provide a new
!         	program (<Application>psql</Application>) which supports <Acronym>GNU</Acronym> <FileName>readline</FileName>.
</Para>
</ListItem>
<ListItem>
<Para>
!       	We added a new  front-end  library,  <FileName>libpgtcl</FileName>,  that
!         	supports  <Acronym>Tcl</Acronym>-based  clients.   A sample shell, 
!         	pgtclsh, provides new Tcl  commands  to  interface  <Application>tcl</Application>
programs with the <ProductName>Postgres95</ProductName> backend.
</Para>
</ListItem>
<ListItem>
<Para>
!       	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.)
</Para>
</ListItem>
<ListItem>
<Para>
!       	The  instance-level  rule  system  has been removed.
!         	Rules are still available as rewrite rules.
</Para>
</ListItem>
<ListItem>
<Para>
A short tutorial introducing regular <Acronym>SQL</Acronym> features as
!         	well as those of ours is distributed with the source
!         	code.
</Para>
</ListItem>
<ListItem>
<Para>
!       	<Acronym>GNU</Acronym> make (instead of  <Acronym>BSD</Acronym>  make)  is  used  for  the
!         	build.  Also,  <ProductName>Postgres95</ProductName>  can  be  compiled with an
!         	unpatched <ProductName>gcc</ProductName> (data alignment of  doubles  has  been
!         	fixed).
</Para>
</ListItem>
</ItemizedList>
--- 91,165 ----
<ULink url="mailto:ayu@informix.com">Andrew Yu</ULink>
and
<ULink url="http://http.cs.berkeley.edu/~jolly/">Jolly Chen</ULink>
! added a SQL language interpreter to <ProductName>Postgres</ProductName>.
! <ProductName>Postgres95</ProductName> was subsequently released to
! the Web to find its own way in the world as a public-domain,
! open source descendant of the original <ProductName>Postgres</ProductName>
! Berkeley code.
</Para>

<Para>
! <ProductName>Postgres95</ProductName> code was completely
! ANSI C and trimmed in size by 25%. Many
! internal changes improved performance and maintainability.
! <ProductName>Postgres95</ProductName> v1.0.x ran about 30-50%
! faster on the Wisconsin Benchmark compared to
! <ProductName>Postgres</ProductName> v4.2.
! Apart from bug fixes, these were the major enhancements:

<ItemizedList>
<ListItem>
<Para>
! The query language <ProductName>Postquel</ProductName> was replaced with
! <Acronym>SQL</Acronym> (implemented in the server). Subqueries were not supported until <ProductName>PostgreSQL</ProductName> (see below), but they
! could be imitated in <ProductName>Postgres95</ProductName> with user-defined
! <Acronym>SQL</Acronym> functions. Aggregates were
! re-implemented. Support for ``GROUP BY'' was also added.
! The <FileName>libpq</FileName> interface remained available for <Acronym>C</Acronym>
programs.
</Para>
</ListItem>
<ListItem>
<Para>
! In addition to the monitor program, a new program
! (<Application>psql</Application>) was provided for interactive SQL queries
! using <Acronym>GNU</Acronym> <FileName>readline</FileName>.
</Para>
</ListItem>
<ListItem>
<Para>
! A new front-end library, <FileName>libpgtcl</FileName>,
! supported <Acronym>Tcl</Acronym>-based clients. A sample shell,
! pgtclsh, provided new Tcl commands to interface <Application>tcl</Application>
programs with the <ProductName>Postgres95</ProductName> backend.
</Para>
</ListItem>
<ListItem>
<Para>
! The large object interface was overhauled. The Inversion large objects were
! the only mechanism for storing large objects.
! (The Inversion file system was removed.)
</Para>
</ListItem>
<ListItem>
<Para>
! The instance-level rule system was removed.
! Rules were still available as rewrite rules.
</Para>
</ListItem>
<ListItem>
<Para>
A short tutorial introducing regular <Acronym>SQL</Acronym> features as
! well as those of <ProductName>Postgres95</ProductName> was
! distributed with the source code.
</Para>
</ListItem>
<ListItem>
<Para>
! <Acronym>GNU</Acronym> make (instead of <Acronym>BSD</Acronym> make) was used
! for the build. Also, <ProductName>Postgres95</ProductName> could be
! compiled with an unpatched <ProductName>gcc</ProductName>
! (data alignment of doubles was fixed).
</Para>
</ListItem>
</ItemizedList>
***************
*** 160,193 ****
<Title><ProductName>PostgreSQL</ProductName></Title>

<Para>
! By 1996, it became clear that the name <Quote>Postgres95</Quote> would not stand
! the test of time. A new name, <ProductName>PostgreSQL</ProductName>,
! was chosen to reflect the
! relationship between original <ProductName>Postgres</ProductName>
! and the more recent
! versions with <Acronym>SQL</Acronym> 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 <ProductName>Postgres</ProductName> Project.
</Para>

<Para>
! The emphasis on development for the v1.0.x releases of
! <ProductName>Postgres95</ProductName>
! was on stabilizing the backend code.
! With the v6.x series of <ProductName>PostgreSQL</ProductName>,
! the emphasis has shifted from
! identifying and understanding existing problems in the backend
! to augmenting features and capabilities, although
work continues in all areas.
</Para>

<Para>
! Major enhancements include:
</Para>

<ItemizedList>
<ListItem>
<Para>
Important backend features, including subselects, defaults, 
--- 170,206 ----
<Title><ProductName>PostgreSQL</ProductName></Title>

<Para>
! By 1996, it became clear that the name <Quote>Postgres95</Quote> would
! not stand the test of time. We chose a new name,
! <ProductName>PostgreSQL</ProductName>, to reflect the relationship
! between the original <ProductName>Postgres</ProductName> and the more
! recent versions with <Acronym>SQL</Acronym> 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
! <ProductName>Postgres</ProductName> Project.
</Para>

<Para>
! The emphasis during development of <ProductName>Postgres95</ProductName>
! was on identifying and understanding existing problems in the backend code.
! With <ProductName>PostgreSQL</ProductName>,
! the emphasis has shifted to augmenting features and capabilities, although
work continues in all areas.
</Para>

<Para>
! Major enhancements in <ProductName>PostgreSQL</ProductName> include:
</Para>

<ItemizedList>
+ <ListItem>
+ <Para>
+ 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.
+ </Para>
+ </ListItem>
<ListItem>
<Para>
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

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

How would you suggest I invoke the patch utility to get this to
work?

1. save patch file to doc/src/sgml/history.sgml.patch
2. cd doc/src/sgml
3. patch < history.sgml.patch

Hmm. Somehow since it had the doc/src/sgml path in the names I put it
up in the top level directory, but it wasn't happy. Didn't try exactly
what you suggest. btw, I'm running the same version of patch as
yourself.

The one thing about renaming the original files to .orig is that I get
confused when doing cvs updates. By keeping all of my changes in .new
files, it's clearer to me which of my changes made it into the
official Postgres repository. But again, I'll do whatever makes it
easier for you.

Well, easiest for me is probably filename.sgml.orig and filename.sgml,
just because that is the form for all of the other patches we get.

btw, you might want to use cvsup to pull over the CVS repository.
Then, you can easily diff and update your local working tree via local
cvs without the risk of blowing away any changes you might have made.
And cvs will show you which files have changed, even if you forget to
rename them or save a .orig version. The newest version of the docs
have an appendix on cvs/cvsup access.

- Thomas

--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California

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