Bruce Momjian <[EMAIL PROTECTED]> writes:
> Please review the HISTORY file.
PostgreSQL now support ALTER TABLE ... DROP COLUMN functionality.
s/support/supports/
Functions can now return sets, with multiple rows
and multiple columns. You specify these functions in
the SELECT FROM clause, similar to a table or view.
I don't like this description: it's always been possible for functions
to return sets, it was just hard to use the feature. Try to explain
what we really added. Maybe:
Functions returning sets (multiple rows) and/or tuples (multiple
columns) are now much easier to use than before. You can call
such a function in the SELECT FROM clause, treating its output
like a table. Such a function can be declared to return RECORD,
with the actual output column set varying from one query to the
next. Also, plpgsql functions can now return sets.
Both multibyte and locale are now enabled by default.
s/enabled by default/always enabled/ --- AFAIK it is impossible to
disable them, so "by default" is pretty misleading.
By default, functions can now take up to 32 parameters, and
identifiers can be up to 64 bytes long.
s/64/63/
Add pg_locks table to show locks (Neil)
s/table/view/
EXPLAIN now outputs as a query (Tom)
This doesn't seem to belong under the Performance heading.
Display sort keys in EXPLAIN (Tom)
Likewise.
Restrict comments to the current database
Should probably say "comments on databases".
Increase maximum number of function parameters to 32 (Bruce)
momjian
This line seems to need editing?
Modify a few error messages for consistency (Bruce)
momjian
This too.
Cleanups in array internal handling (Tom)
Joe should get credit on that one.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
