code would cluster, but table would magically lose its tempness.

(i.e., 7.0.3) of libpostgres.a.  From Jason Tishler <jt@dothill.com>.

entry:

----------------------------
revision 1.2
date: 2000/12/04 01:20:38;  author: tgl;  state: Exp;  lines:
+18 -18
Eliminate some of the more blatant platform-dependencies ... it
builds here now, anyway ...
----------------------------

Which basically changes u_int*_t -> uint*_t, so now it does not
compile neither under Debian 2.2 nor under NetBSD 1.5 which
is platform independent<B8> all right.  Also it replaces $KAME$
with $Id$ which is Bad Thing. PostgreSQL Id should be added as a
separate line so the file history could be seen.

So here is patch:

* changes uint*_t -> uint*.  I guess that was the original
  intention
* adds uint64 type to include/c.h because its needed
  [somebody should check if I did it right]
* adds back KAME Id, because KAME is the master repository
* removes stupid c++ comments in pgcrypto.c
* removes <sys/types.h> from the code, its not needed

--
marko

Marko Kreen

It adds information about SQL JOIN that is implemented in 7.1.

--
-------- Robert B. Easter

EXECUTE.

--
-------- Robert B. Easter

find it ambiguous.  I propose something along the lines of the
following patch to clarify it.  Thanks.

(Alternatively, perhaps the code could maintain a count of nested
calls to SPI_connect/SPI_finish.  But I didn't try to write that
patch.)

Ian Lance Taylor

jump version to beta3 ... beta2 was created and pulled due to a couple of
large-ish bugs that Tom and Vadim were able to fix, but to avoid any
confusion, beta2 was removed ... and for tag'ng purposes, beta3 is being
created ...

Chih-Chang Hsieh <cch@cc.kmu.edu.tw>, written in traditional Chinese
(Big5).

   - no more elog(STOP) in StartupXLOG();
   - both checkpoint' undo & redo are used to define
     oldest on-line log file.
2. Ability to pre-allocate a few log files at checkpoint time
   (wal_files option). Off by default.

as both a GROUP BY item and an output expression, the top-level Group
node should just copy up the evaluated expression value from its input,
rather than re-evaluating the expression.  Aside from any performance
benefit this might offer, this avoids a crash when there is a sub-SELECT
in said expression.

were never yet mentioned anywhere in our documentation.  Improve
explanations of the other system attributes, too.

the output of UNION/INTERSECT/EXCEPT.

inconsistent coding practices for handling Index values and booleans,
too.

before calling RelationInvalidateHeapTuple(), which is bad because the
latter needs to look at the tuple data, which is in the shared disk
buffer.  If another backend manages to recycle the buffer while this
is going on, we will compute the wrong hashindex for the tuple or
maybe even crash outright.  Must hold buffer refcount until afterwards.
(This bug is not in 7.0.*; seems to be have introduced during WAL changes.)

that leftover cancel/die requests cannot interfere with exit activities.

of 6 Jan 2001 21:55.

tag configure as beta2 ..

and burn.  Just for added luck, change reading of CONST nodes so that
we do not need to consult pg_type rows while reading them; this means
that no database access occurs during stringToNode.  This requires
changing the order in which const-node fields are written, which means
an initdb is forced.

Disallow cases like adding constraints to sequences :-(, and eliminate
now-unnecessary search of pg_rewrite to decide if a relation is a view.

error, so as to provide a starting point for debugging.