this file in interfaces/

It will all need to be checked in.  I used the char *rcsid[] method for
cvs ids so it can be strings | grep'd to find version numbers.  The new
version for the library is 3.0.

Run configure from src/ to create the Makefile and it should be good to
go.

I did minimal documentation references in the README, I'll see if I can
get something to Tom Lockhart rather quickly.

Vince.

This agrees with the documentation and seems like a more useful default
anyhow ...

bigger the more space is used in an allocset.  This reduces the malloc
overhead very substantially on queries that need lots of memory.

kernel's error description when file is not accessible).

symbolic LOW/MEDIUM/HIGH values --- needed for experiments with other
effort levels ...

from being accepted when they are passed from client connection request.
Get rid of a couple that no longer do anything (like -P).

 and the integrated doc. Clean up other markup.

update material about client connection failure messages.

failure messages.

clauses in CREATE OPERATOR.  Needs markup work.

from initdb again.

Added two new commands, createlang and destroylang to bin. These
hopefully end this damned mklang.sql discussion.

Jan

and trigger function found but returns wrong type.

SelectStmt and CursorStmt tried to parse FOR UPDATE ... / FOR READ ONLY.
Cursor now checks that it is read only by looking at forUpdate of Query.
SelectStmt handles FOR READ ONLY too.

Jan

Add reference pages for utilities and remove standalone chapters for same.
Add material for an appendix on date/time properties, but not yet
 integrated with the User's Guide.
Break up the former chapter on pg_options
 into Admin and Programmer's Guides.

INTERNAL functions, add a warning about trying to overload function names
for dynamically loaded C functions (from old man page).

many moons ago, but forgot to put here.

entries (prosrc is now name of C-level function).

Bring python up to date ...

From: D'Arcy J.M. Cain <darcy@druid.net>

will pass through rather than spitting up.  This is necessary to handle
cases where coerce_type causes a subexpression to be retransformed, as in
	SELECT count(*) + 1.0 FROM table