Log Message:
---
Add sinh, cosh, tanh and nanvl.
Modified Files:
--
orafce:
README.orafunc (r1.29 -> r1.30)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/README.orafunc.diff?r1=1.29&r2=1.30)
orafunc.sql.in (r1.44 -> r1.45)
(htt
Log Message:
---
Modify the parser's error reporting to include a specific hint for the case
of referencing a WITH item that's not yet in scope according to the SQL
spec's semantics. This seems to be an easy error to make, and the bare
"relation doesn't exist" message doesn't lead one's mi
Log Message:
---
Suppress some complier warnings.
Modified Files:
--
psqlodbc:
environ.c (r1.71 -> r1.72)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/psqlodbc/psqlodbc/environ.c.diff?r1=1.71&r2=1.72)
info.c (r1.153 -> r1.154)
(http://cvs.p
Log Message:
---
Update Japanese FAQ.
Jun Kuwamura
Modified Files:
--
pgsql/doc:
FAQ_japanese (r1.52 -> r1.53)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_japanese?r1=1.52&r2=1.53)
pgsql/doc/src/FAQ:
FAQ_japanese.html (r1.53 -> r1.5
Log Message:
---
Improve some of the comments in fsmpage.c.
Modified Files:
--
pgsql/src/backend/storage/freespace:
fsmpage.c (r1.1 -> r1.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/freespace/fsmpage.c?r1=1.1&r2=1.2)
--
Sent via
Log Message:
---
Extend CTE patch to support recursive UNION (ie, without ALL). The
implementation uses an in-memory hash table, so it will poop out for very
large recursive results ... but the performance characteristics of a
sort-based implementation would be pretty unpleasant too.
Modi
Log Message:
---
Synced parser.
Modified Files:
--
pgsql/src/interfaces/ecpg:
ChangeLog (r1.386 -> r1.387)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/ChangeLog?r1=1.386&r2=1.387)
pgsql/src/interfaces/ecpg/preproc:
prepro
Log Message:
---
When a relation is moved to another tablespace, we can't assume that we can
use the old relfilenode in the new tablespace. There might be another relation
in the new tablespace with the same relfilenode, so we must generate a fresh
relfilenode in the new tablespace.
The 8.
Log Message:
---
When a relation is moved to another tablespace, we can't assume that we can
use the old relfilenode in the new tablespace. There might be another relation
in the new tablespace with the same relfilenode, so we must generate a fresh
relfilenode in the new tablespace.
The 8.
Log Message:
---
When a relation is moved to another tablespace, we can't assume that we can
use the old relfilenode in the new tablespace. There might be another relation
in the new tablespace with the same relfilenode, so we must generate a fresh
relfilenode in the new tablespace.
The 8.
Log Message:
---
When a relation is moved to another tablespace, we can't assume that we can
use the old relfilenode in the new tablespace. There might be another relation
in the new tablespace with the same relfilenode, so we must generate a fresh
relfilenode in the new tablespace.
The 8.
11 matches
Mail list logo