recent discussion.  The lexer is used for both SQL command text and
backslash commands.  The purpose of this change is to make it easier to
track the behavior of the backend's SQL lexer --- essentially identical
flex rules are now used by psql.  Also, this cleans up a lot of very
squirrelly code in mainloop.c and command.c.  The flex code is somewhat
bulkier than the removed code, but should be lots easier to maintain.

backend lexer against psql's.

< * Add GUC variable to prevent waiting on locks
> * Add NO WAIT option to various SQL commands

applied, deadlock detection and statement_timeout now works.

The file timer.c goes into src/backend/port/win32/.

The patch also removes two lines of "printf debugging" accidentally left
in pqsignal.h, in the console control handler.

Magnus Hagander

invalid input to the oid type. Also, remove some long-unused code
from adt/numutils.c

better job of handling dependencies between database objects.

> * -Change CVS ID to PostgreSQL

> 	o Allow the schema of objects to be changed

patch from Michael Glaesemann, additional changes by Neil Conway.

vacuum delay feature, including updating the docs for Tom's recent
improvements. There is still more work to be done here: for example,
adding some more information on the practical use of cost-based
vacuum delay to the "maintenance" section would probably be a good
idea.

patch.

bitrotted) to allow the logging of the end of a session, enabled by
the config setting "log_disconnections".

Andrew Dunstan

1) Now puts in exactly the same change as the current-cvs mingw code
does. (see
http://cvs.sourceforge.net/viewcvs.py/mingw/runtime/mingwex/dirent.c?r1=
1.3&r2=1.4, second part of the patch).

2) Updates both xlog.c and slru.c in backend/access/transam/

3) Also updates pg_resetxlog, which also uses readdir() and checks the
errno value after the loop.

Magnus Hagander

Win2K, and possibly all Win32 variants, it is always 0). This causes a
number of problems in the dfmgr.c logic, which basically all revolve
around the fact that *any* two files will appear to have the same inode.

Claudio Natoli

In incorperates changes from myself and a number of contributors.

This update to dbmirror provides:

-replication of sequence operations via setval/nextval
-DBMirror.pl support for logging to syslog
-changed the names of the tables to dbmirror_*  (no quotes required)
-Support for writitng SQL statements to files instead of directly to
 a slave database
-More options for DBMirror.pl in the config files.

Steven Singer

corner cases that could stand improvement, but it does all the basic
stuff.  A byproduct is that the selectivity routines are no longer
constrained to working on simple Vars; we might in future be able to
improve the behavior for subexpressions that don't match indexes.

  typename to be typedef'ed that cannot be parsed as variable type.
- Allowed some SQL keywords to be used as C variable names.

This commit teaches ANALYZE to store such stats in pg_statistic, but
nothing is done yet about teaching the planner to use 'em.
Also, repair longstanding oversight in separate ANALYZE command: it
updated the pg_class.relpages and reltuples counts for the table proper,
but not for indexes.

	- Set ecpg version to 3.1.1.
	- Removed that old debugging output that I forgot the last time.

vs. timestamptz.  This allows use of indexes for expressions like
  datecol >= date 'today' - interval '1 month'
which were formerly not indexable without casting the righthand side
down from timestamp to date.

Nov 2002: when constant-expression simplification removes all the
aggregate function calls from a query, that doesn't mean we can act as
though there never were any aggregates.  Per bug report from Gabor Szucs.

Jan

indexes, it seems like we ought to put another layer of indirection
between the compute_stats functions and the actual data storage.  This
would allow us to compute the values on-the-fly, for example.

< * Allow cross-db queries with transaction sematics
> * Allow cross-db queries with transaction semantics

> momjian@svr1.postgresql.org (Bruce Momjian) writes:
>>      someone asked me about the FK deadlock fix, mentioned in the 7.3.3
>>      release notes as 3rd change:
>>      http://www.postgresql.org/docs/current/static/release-7-3-3.html
>>      Actually, that fix was available with 7.4, not 7.3. Don't know if we can
>>      retroactively change the release-notes though.
>
> This is completely erroneous, please undo it.
>
> 2003-05-21 14:14  tgl
>
>       * src/: backend/utils/adt/ri_triggers.c,
>       test/regress/expected/foreign_key.out (REL7_3_STABLE): Back-patch
>       Jan's fix to avoid primary key lookup (and lock) if foreign key
>       does not change on UPDATE.

Oh ... didn't know that you did a backpatch. Sorry


Jan

> * Use nested transactions to prevent syntax errors from aborting a transaction

> * Allow temporary views on non-temporary tables

bit more helpful by identifying the specific qualified name being
complained of.

coding by Mark Cave-Ayland, some kibitzing by Tom Lane.  initdb forced
due to new column in pg_type.