database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-11-12 05:01:15 +03:00
Code Activity

Label CVS tip as 8.0devel instead of 7.5devel. Adjust various comments

Browse Source 
and documentation to reference 8.0 instead of 7.5.
This commit is contained in:
Tom Lane
2004-08-04 21:34:35 +00:00
parent ecb68138e9
commit fcbc438727
73 changed files with 157 additions and 157 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/backend/utils/adt/float.c
View File

@@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/utils/adt/float.c,v 1.105 2004/05/16 23:18:55 neilc Exp $
* $PostgreSQL: pgsql/src/backend/utils/adt/float.c,v 1.106 2004/08/04 21:34:02 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -259,10 +259,10 @@ float4in(PG_FUNCTION_ARGS)
* Check for an empty-string input to begin with, to avoid
* the vagaries of strtod() on different platforms.
*
* In releases prior to 7.5, we accepted an empty string as valid
* input (yielding a float4 of 0). In 7.5, we accept empty
* In releases prior to 8.0, we accepted an empty string as valid
* input (yielding a float4 of 0). In 8.0, we accept empty
* strings, but emit a warning noting that the feature is
* deprecated. In 7.6+, the warning should be replaced by an
* deprecated. In 8.1+, the warning should be replaced by an
* error.
*/
if (*num == '\0')
@@ -424,10 +424,10 @@ float8in(PG_FUNCTION_ARGS)
* Check for an empty-string input to begin with, to avoid
* the vagaries of strtod() on different platforms.
*
* In releases prior to 7.5, we accepted an empty string as valid
* input (yielding a float8 of 0). In 7.5, we accept empty
* In releases prior to 8.0, we accepted an empty string as valid
* input (yielding a float8 of 0). In 8.0, we accept empty
* strings, but emit a warning noting that the feature is
* deprecated. In 7.6+, the warning should be replaced by an
* deprecated. In 8.1+, the warning should be replaced by an
* error.
*/
if (*num == '\0')

8
src/backend/utils/adt/oid.c
View File

@@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/utils/adt/oid.c,v 1.56 2004/03/11 02:11:13 neilc Exp $
* $PostgreSQL: pgsql/src/backend/utils/adt/oid.c,v 1.57 2004/08/04 21:34:02 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -34,10 +34,10 @@ oidin_subr(const char *funcname, const char *s, char **endloc)
Oid result;
/*
* In releases prior to 7.5, we accepted an empty string as valid
* input (yielding an OID of 0). In 7.5, we accept empty strings,
* In releases prior to 8.0, we accepted an empty string as valid
* input (yielding an OID of 0). In 8.0, we accept empty strings,
* but emit a warning noting that the feature is deprecated. In
* 7.6+, the warning should be replaced by an error.
* 8.1+, the warning should be replaced by an error.
*/
if (*s == '\0')
ereport(WARNING,

4
src/backend/utils/adt/selfuncs.c
View File

@@ -15,7 +15,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/utils/adt/selfuncs.c,v 1.161 2004/06/11 01:09:04 tgl Exp $
* $PostgreSQL: pgsql/src/backend/utils/adt/selfuncs.c,v 1.162 2004/08/04 21:34:02 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -4294,7 +4294,7 @@ btcostestimate(PG_FUNCTION_ARGS)
* from pg_statistic, estimate the index correlation as C for a single-
* column index, or C * 0.75 for multiple columns. (The idea here is
* that multiple columns dilute the importance of the first column's
* ordering, but don't negate it entirely. Before 7.5 we divided the
* ordering, but don't negate it entirely. Before 8.0 we divided the
* correlation by the number of columns, but that seems too strong.)
*/
if (index->indexkeys[0] != 0)

4
src/backend/utils/fmgr/funcapi.c
View File

@@ -7,7 +7,7 @@
* Copyright (c) 2002-2003, PostgreSQL Global Development Group
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/utils/fmgr/funcapi.c,v 1.14 2004/04/01 21:28:45 tgl Exp $
* $PostgreSQL: pgsql/src/backend/utils/fmgr/funcapi.c,v 1.15 2004/08/04 21:34:03 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -106,7 +106,7 @@ per_MultiFuncCall(PG_FUNCTION_ARGS)
* at the beginning of each call, the Slot will hold a dangling
* pointer to an already-recycled tuple. We clear it out here.
*
* Note: use of retval->slot is obsolete as of 7.5, and we expect that
* Note: use of retval->slot is obsolete as of 8.0, and we expect that
* it will always be NULL. This is just here for backwards compatibility
* in case someone creates a slot anyway.
*/

4
src/backend/utils/mmgr/README
View File

@@ -1,4 +1,4 @@
$PostgreSQL: pgsql/src/backend/utils/mmgr/README,v 1.7 2004/07/01 00:51:29 tgl Exp $
$PostgreSQL: pgsql/src/backend/utils/mmgr/README,v 1.8 2004/08/04 21:34:04 tgl Exp $
Notes about memory allocation redesign
--------------------------------------
@@ -66,7 +66,7 @@ return NULL, and it is not necessary or useful to test for such a result.
* palloc(0) is explicitly a valid operation. It does not return a NULL
pointer, but a valid chunk of which no bytes may be used. (However, the
chunk might later be repalloc'd larger; it can also be pfree'd without
error.) (Note: this behavior is new in Postgres 7.5; earlier versions
error.) (Note: this behavior is new in Postgres 8.0; earlier versions
disallowed palloc(0). It seems more consistent to allow it, however.)
Similarly, repalloc allows realloc'ing to zero size.