between Postgres and PostgreSQL.

information about nulls and sort order.

This is based on information obtained from Peter Eisentraut and
Tom Lane on pgsql-hackers.

Please check my English and Docbook markup, as both are a second
language to me.

Rene Pijlman

Alvaro Herrera

	* Change LIMIT val,val to offset,limit to match MySQL

Documentation updates too.

privileges.  INSERT and COPY FROM now require INSERT (only).  Add
privileges regression test.

(inadequate anyway) mention of SELECT INTO from the main SELECT ref page.
Point out that SELECT INTO means something else in plpgsql and ecpg.

the endterm to the title element, not both to the title.  At least
docbook2man prefers it that way.

etc.

the output of UNION/INTERSECT/EXCEPT.

ISO-compliant UNION/INTERSECT/EXCEPT.  Revise discussion of rule
rewriter to reflect new subselect-in-FROM implementation of views.
Miscellaneous other cleanups.

Fix misspelling of disbursion to dispersion.

option settings. Sort out SIGHUP vs BACKEND -- there is no total ordering
here, so make explicit checks. Add comments explaining all of this.
Removed permissions check on SHOW command.

Add examine_subclass to the game, rename to SQL_inheritance to fit the
official data model better. Adjust documentation.

Standalone backend needs to reset all options before it starts. To
facilitate that, have IsUnderPostmaster be set by the postmaster itself,
don't wait for the magic -p switch.

Also make sure that all environment variables and argv's survive
init_ps_display(). Use strdup where necessary.

Have initdb make configuration files (postgresql.conf, pg_hba.conf) mode
0600 -- having configuration files is no fun if you can't edit them.

Use "generic functions" for math and other routines.
Use SQL92 "type 'literal'" syntax rather than Postgres "'literal'::type".

Fixed bug in createdb/alternative location

after trying to resolve the item as an input-column name.  This allows us
to be compliant with the SQL92 spec for queries that fall within the spec,
while still accepting the same out-of-spec queries as 6.5 did.  You'll only
lose if there is an output column name that is the same as an input
column name, but doesn't refer to the same value.  7.0 will interpret
such a GROUP BY spec differently than 6.5 did.  No way around that, because
6.5 was clearly not spec compliant.

of LIMIT, and fix a few other glitches too.

SELECT DISTINCT ON (expr [, expr ...]) targetlist ...
and there is a check to make sure that the user didn't specify an ORDER BY
that's incompatible with the DISTINCT operation.
Reimplement nodeUnique and nodeGroup to use the proper datatype-specific
equality function for each column being compared --- they used to do
bitwise comparisons or convert the data to text strings and strcmp().
(To add insult to injury, they'd look up the conversion functions once
for each tuple...)  Parse/plan representation of DISTINCT is now a list
of SortClause nodes.
initdb forced by querytree change...

Try to provide a more lucid discussion in 'Using Aggregate Functions'
tutorial section.

Add new pages for programming languages and tcl shells.

ecpg reference page still needs formatting.

Add some internal cross references to select.sgml.

Split reference pages for CREATE TABLE AS and SELECT INTO to allow psgml
 (the emacs parser) to handle parsing.

Required by newest versions of DocBook and style sheets.