database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-09-08 00:47:37 +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

4
src/backend/access/transam/xlog.c
View File

@@ -7,7 +7,7 @@
* Portions Copyright (c) 1996-2003, PostgreSQL Global Development Group
* Portions Copyright (c) 1994, Regents of the University of California
*
* $PostgreSQL: pgsql/src/backend/access/transam/xlog.c,v 1.155 2004/08/04 16:25:02 tgl Exp $
* $PostgreSQL: pgsql/src/backend/access/transam/xlog.c,v 1.156 2004/08/04 21:33:46 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -4588,7 +4588,7 @@ ReadCheckpointRecord(XLogRecPtr RecPtr,
* instead). We need to initialize the local copies of ThisTimeLineID and
* RedoRecPtr.
*
* Note: before Postgres 7.5, we went to some effort to keep the postmaster
* Note: before Postgres 8.0, we went to some effort to keep the postmaster
* process's copies of ThisTimeLineID and RedoRecPtr valid too. This was
* unnecessary however, since the postmaster itself never touches XLOG anyway.
*/

4
src/backend/catalog/catalog.c
View File

@@ -9,7 +9,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/catalog/catalog.c,v 1.54 2004/06/21 04:06:05 tgl Exp $
* $PostgreSQL: pgsql/src/backend/catalog/catalog.c,v 1.55 2004/08/04 21:33:47 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -199,7 +199,7 @@ IsToastNamespace(Oid namespaceId)
* True iff name starts with the pg_ prefix.
*
* For some classes of objects, the prefix pg_ is reserved for
* system objects only. As of 7.5, this is only true for
* system objects only. As of 8.0, this is only true for
* schema and tablespace names.
*/
bool

4
src/backend/commands/indexcmds.c
View File

@@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/commands/indexcmds.c,v 1.122 2004/06/18 06:13:23 tgl Exp $
* $PostgreSQL: pgsql/src/backend/commands/indexcmds.c,v 1.123 2004/08/04 21:33:48 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -539,7 +539,7 @@ GetIndexOpClass(List *opclass, Oid attrType,
* too for awhile. I'm starting to think we need a better approach.
* tgl 2000/10/01
*
* Release 7.5 removes bigbox_ops (which was dead code for a long while
* Release 8.0 removes bigbox_ops (which was dead code for a long while
* anyway). tgl 2003/11/11
*/
if (list_length(opclass) == 1)

4
src/backend/libpq/be-fsstubs.c
View File

@@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/libpq/be-fsstubs.c,v 1.71 2004/07/28 14:23:28 tgl Exp $
* $PostgreSQL: pgsql/src/backend/libpq/be-fsstubs.c,v 1.72 2004/08/04 21:33:49 tgl Exp $
*
* NOTES
* This should be moved to a more appropriate place. It is here
@@ -27,7 +27,7 @@
* existing documented semantics of LO FDs: they're only good within a
* transaction.
*
* As of PostgreSQL 7.5, much of the angst expressed above is no longer
* As of PostgreSQL 8.0, much of the angst expressed above is no longer
* relevant, and in fact it'd be pretty easy to allow LO FDs to stay
* open across transactions. However backwards compatibility suggests
* that we should stick to the status quo.

4
src/backend/nodes/list.c
View File

@@ -9,7 +9,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/nodes/list.c,v 1.59 2004/06/01 06:02:12 tgl Exp $
* $PostgreSQL: pgsql/src/backend/nodes/list.c,v 1.60 2004/08/04 21:33:51 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -251,7 +251,7 @@ lappend_cell_oid(List *list, ListCell *prev, Oid datum)
* value, rather than continuing to use the pointer passed as the
* second argument.
*
* Caution: before Postgres 7.5, the original List was unmodified and
* Caution: before Postgres 8.0, the original List was unmodified and
* could be considered to retain its separate identity. This is no longer
* the case.
*/

4
src/backend/optimizer/path/costsize.c
View File

@@ -49,7 +49,7 @@
* Portions Copyright (c) 1994, Regents of the University of California
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/optimizer/path/costsize.c,v 1.131 2004/06/10 21:02:00 tgl Exp $
* $PostgreSQL: pgsql/src/backend/optimizer/path/costsize.c,v 1.132 2004/08/04 21:33:54 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -238,7 +238,7 @@ cost_nonsequential_access(double relpages)
* tuples, but they won't reduce the number of tuples we have to fetch from
* the table, so they don't reduce the scan cost.
*
* NOTE: as of 7.5, indexQuals is a list of RestrictInfo nodes, where formerly
* NOTE: as of 8.0, indexQuals is a list of RestrictInfo nodes, where formerly
* it was a list of bare clause expressions.
*/
void

4
src/backend/optimizer/path/indxpath.c
View File

@@ -9,7 +9,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/optimizer/path/indxpath.c,v 1.161 2004/06/01 04:47:45 tgl Exp $
* $PostgreSQL: pgsql/src/backend/optimizer/path/indxpath.c,v 1.162 2004/08/04 21:33:54 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -980,7 +980,7 @@ static const StrategyNumber
* operator class. We use the above operator implication table to be able to
* derive implications between nonidentical clauses. (Note: "foo" is known
* immutable, and constants are surely immutable, but we have to check that
* the operators are too. As of 7.5 it's possible for opclasses to contain
* the operators are too. As of 8.0 it's possible for opclasses to contain
* operators that are merely stable, and we dare not make deductions with
* these.)
*

4
src/backend/optimizer/util/pathnode.c
View File

@@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/optimizer/util/pathnode.c,v 1.107 2004/06/01 03:03:02 tgl Exp $
* $PostgreSQL: pgsql/src/backend/optimizer/util/pathnode.c,v 1.108 2004/08/04 21:33:55 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@@ -286,7 +286,7 @@ add_path(RelOptInfo *parent_rel, Path *new_path)
int costcmp;
/*
* As of Postgres 7.5, we use fuzzy cost comparison to avoid wasting
* As of Postgres 8.0, we use fuzzy cost comparison to avoid wasting
* cycles keeping paths that are really not significantly different
* in cost.
*/

4
src/backend/po/ru.po
View File

@@ -1,10 +1,10 @@
# ru.po
# POSTGRES Translated Messages into the Russian Language (KOI8-R)
#
# $Header: /cvsroot/pgsql/src/backend/po/Attic/ru.po,v 1.17 2004/07/02 15:07:10 petere Exp $
# $Header: /cvsroot/pgsql/src/backend/po/Attic/ru.po,v 1.18 2004/08/04 21:33:57 tgl Exp $
#
# ChangeLog:
# - March 27 - June 24, 2004: updates for 7.4 - 7.5 branches; <mokhov@cs.concordia.ca>
# - March 27 - June 24, 2004: updates for 7.4 - 8.0 branches; <mokhov@cs.concordia.ca>
# - July - August 23, 2003: updates for 7.4.x; <mokhov@cs.concordia.ca>
# - January 2, 2003: Fuzzy Fixes, Serguei A. Mokhov <mokhov@cs.concordia.ca>
# - October 12, 2002: Post-7.3 beta 2, Fuzzy Fixes, Serguei A. Mokhov <mokhov@cs.concordia.ca>

2
src/backend/po/sv.po
View File

@@ -3,7 +3,7 @@
#
msgid ""
msgstr ""
"Project-Id-Version: PostgreSQL 7.5\n"
"Project-Id-Version: PostgreSQL 8.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2004-06-25 15:07+0200\n"
"PO-Revision-Date: 2004-06-27 11:33+0200\n"

2
src/backend/po/zh_TW.po
View File

@@ -3,7 +3,7 @@
#
msgid ""
msgstr ""
"Project-Id-Version: PostgreSQL 7.5\n"
"Project-Id-Version: PostgreSQL 8.0\n"
"POT-Creation-Date: 2004-08-02 19:00-0300\n"
"PO-Revision-Date: 2004-08-03 13:42+0800\n"
"Last-Translator: Zhenbang Wei <forth@zbwei.net>\n"

4
src/backend/postmaster/bgwriter.c
View File

@@ -2,7 +2,7 @@
*
* bgwriter.c
*
* The background writer (bgwriter) is new in Postgres 7.5. It attempts
* The background writer (bgwriter) is new in Postgres 8.0. It attempts
* to keep regular backends from having to write out dirty shared buffers
* (which they would only do when needing to free a shared buffer to read in
* another page). In the best scenario all writes from shared buffers will
@@ -37,7 +37,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/postmaster/bgwriter.c,v 1.5 2004/08/04 16:24:26 tgl Exp $
* $PostgreSQL: pgsql/src/backend/postmaster/bgwriter.c,v 1.6 2004/08/04 21:34:00 tgl Exp $
*
*-------------------------------------------------------------------------
*/

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.