for join-relations. Sizes already computed by
prune_rel_paths():compute_joinrel_size().

joinrels.c:
<                   if ( _use_right_sided_plans_ )
---
>                   if ( _use_right_sided_plans_ &&
>                               length (outer_rel->relids) > 1 )

 - r_plans are useful when outer_rel is join-relation... It
decreases the size of search space...

the relation from the relcache.

 *         RelationFlushRelation + if the relation is local then get rid of
 *         the relation descriptor from the newly created relation list.

Include paragraph on upgrading old databases containing path or polygon types.

reference platform (Linux/gcc-lib/i686).

Order in streets.data changed and is now alphabetical (sorry).

string.

Include section on error message differences.

upgrading from existing pre-v6.1 path and polygon geometric data types.

migration from pre-v6.1 geometric data types.
Only allow new input syntax for paths and polygons.

dt.c: In function `timespan2tm':
dt.c:1722: warning: unused variable `funit'
dt.c:1722: warning: unused variable `iunit'

-> got rid of them.

to last specified with 'on' #.
What is better ?

remove.c: In function `RemoveAggregate':
remove.c:413: warning: unused variable `typename'

-> got rid of it.

        ^^ - added

psql.c: In function `HandleSlashCmds':
psql.c:1141: warning: `optarg3' might be used uninitialized in this function
psql.c:1157: warning: `optarg3' might be used uninitialized in this function

-> char           *optarg3 = NULL;

start time equal to tuple->t_tmax.

Privent shrinking if there are tuples modifyed by running transactions
(it concerns system relations only, currently).

moved from geqo.h to internal.h.

(both are settable via SET geqo TO ...).

             ^^ is supported by get_token now.
(SET geqo TO 'on=XXX' works now).

Subject: [PATCHES] patch for a memory leak

Well...I screwed up and posted the wrong patch for psql originally..
The patch for that patch wposted below will fix it..

Subject: [PATCHES] INSTALL patch

This patch makes the following changes to the INSTALL instructions:
  - Before step 1, describe disk space requirements.
  - Step 1 now defines a "tested" platform.
  - Add step 3a on checking for disk space.
  - Added new step 27 asking for feedback.

Subject: [PATCHES] Another destroydb patch

This is a patch to my previous destroydb patch cause some people wanted
slightly different behavior. After this patch is applied, destroydb
will destroy a database as usual, but if added -i flag (which could be
aliased like rm -i) would ask for confirmation.