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.

> 	o Modify array literal representation to handle array index lower bound
> 	  of other than one
>
183d185
<

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.

where signals do not terminate sleep() delays.

Update TODO accordingly.

<
<
< Reporting
< =========
<
< * Show location of syntax error in query [yacc]

.< * Improve speed with indexes (perhaps recreate index instead) [vacuum]
> * Improve speed with indexes (perhaps recreate index instead)
369c369
<   lock and truncate table [vacuum]
>   lock and truncate table
371c371
<   rather than in /contrib [vacuum]
>   rather than in /contrib

< * Allow better handling of numeric constants, type conversion [typeconv]

< * Add replication of distributed databases [replication]
> * Add replication of distributed databases

< 	o http://gborg.postgresql.org/project/pgreplication/projdisplay.php

< * Allow persistent backends [persistent]
> * Allow persistent backends [pool]
397c397
<   connection pooling
>   connection pooling [pool]

<   float4, numeric/decimal too [optimizer]
>   float4, numeric/decimal too
422c422
< * Missing optimizer selectivities for date, r-tree, etc. [optimizer]
> * Missing optimizer selectivities for date, r-tree, etc

< * Delay fsync() when other backends are about to commit too [fsync]
> * Delay fsync() when other backends are about to commit too

< * Add MATCH PARTIAL referential integrity [foreign]
> * Add MATCH PARTIAL referential integrity

> * Allow cross-db queries with transaction sematics

< * Allow queries across multiple databases [crossdb]

On Mon, 2004-01-26 at 21:28, Peter Eisentraut wrote:
> Christophe Combelles wrote:
> > At the bottom of this doc file :
> > file:///usr/share/doc/postgresql-doc/html/tutorial-createdb.html
> > "and it also happens that that user always has permission"
> >                       ---- x2
> The first "that" serves as a conjuction, the second one serves as an
> article.  Looks correct to me.

A better workaround for the sentence would be something like:

        "and it also happens that the user always has permission"

Looks easier to read, I think.

Enver ALTIN (a.k.a. skyblue)