Commit8cb3ad9

committed

Revert sentence removal from nickname in FAQ.

1 parent20c5542 commit8cb3ad9Copy full SHA for 8cb3ad9

File tree

+16

-14

lines changed

+16

-14

lines changed

Lines changed: 5 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -10,7 +10,7 @@`
`10`	`10`	`alink="#0000ff">`
`11`	`11`	`<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>`
`12`	`12`
`13`		`-<P>Last updated:Tue Apr 8 20:43:08 EDT 2008</P>`
	`13`	`+<P>Last updated:Mon Mar 3 11:22:50 EST 2008</P>`
`14`	`14`
`15`	`15`	`<P>Current maintainer: Bruce Momjian (<Ahref=`
`16`	`16`	`"mailto:bruce@momjian.us">bruce@momjian.us</A>)`
`@@ -150,8 +150,10 @@ <H3 id="item1.1">1.1) What is PostgreSQL? How is it pronounced? What is Postgres`
`150`	`150`	`http://www.postgresql.org/docs/faqs.FAQ_DEV.html</A>`
`151`	`151`	`</P>`
`152`	`152`
`153`		`-<P>Postgres is a widely-used nickname for PostgreSQL. If you find`
`154`		`- 'PostgreSQL' hard to pronounce, call it 'Postgres' instead.</P>`
	`153`	`+<P>Postgres is a widely-used nickname for PostgreSQL. It was the`
	`154`	`+ original name of the project at Berkeley and is strongly preferred`
	`155`	`+ over other nicknames. If you find 'PostgreSQL' hard to pronounce, call`
	`156`	`+ it 'Postgres' instead.</P>`
`155`	`157`
`156`	`158`	`<H3id="item1.2">1.2) Who controls PostgreSQL?<BR></H3>`
`157`	`159`

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-$PostgreSQL: pgsql/src/backend/optimizer/README,v 1.43 2008/03/21 13:23:28 momjian Exp $`
	`1`	`+$PostgreSQL: pgsql/src/backend/optimizer/README,v 1.44 2008/04/09 00:55:30 momjian Exp $`
`2`	`2`
`3`	`3`	`Optimizer`
`4`	`4`	`=========`
`@@ -73,8 +73,8 @@ tree is found by a recursive process:`
`73`	`73`
`74`	`74`	`1) Take each base relation in the query, and make a RelOptInfo structure`
`75`	`75`	`for it. Find each potentially useful way of accessing the relation,`
`76`		`-including sequential and index scans, and makea Pathrepresentingthat`
`77`		`-way. All the Paths made for a given relation are placed in its`
	`76`	`+including sequential and index scans, and makePathsrepresentingthose`
	`77`	`+ways. All the Paths made for a given relation are placed in its`
`78`	`78`	`RelOptInfo.pathlist. (Actually, we discard Paths that are obviously`
`79`	`79`	`inferior alternatives before they ever get into the pathlist --- what`
`80`	`80`	`ends up in the pathlist is the cheapest way of generating each potentially`
`@@ -271,7 +271,7 @@ The primary entry point is planner().`
`271`	`271`
`272`	`272`	`planner()`
`273`	`273`	`set up for recursive handling of subqueries`
`274`		`- do final cleanup after planning.`
	`274`	`+ do final cleanup after planning`
`275`	`275`	`-subquery_planner()`
`276`	`276`	`pull up subqueries from rangetable, if possible`
`277`	`277`	`canonicalize qual`

Lines changed: 3 additions & 3 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-$PostgreSQL: pgsql/src/backend/parser/README,v 1.7 2008/03/21 13:23:28 momjian Exp $`
	`1`	`+$PostgreSQL: pgsql/src/backend/parser/README,v 1.8 2008/04/09 00:55:30 momjian Exp $`
`2`	`2`
`3`	`3`	`Parser`
`4`	`4`	`======`
`@@ -14,13 +14,13 @@ keywords.cturn keywords into specific tokens`
`14`	`14`	`gram.yparse the tokens and fill query-type-specific structures`
`15`	`15`	`analyze.ctop level of parse analysis for optimizable queries`
`16`	`16`	`parse_clause.chandle clauses like WHERE, ORDER BY, GROUP BY, ...`
`17`		`-parse_coerce.chandle coercing expressions to different types`
	`17`	`+parse_coerce.chandle coercing expressions to differentdatatypes`
`18`	`18`	`parse_expr.chandle expressions like col, col + 3, x = 3 or x = 4`
`19`	`19`	`parse_oper.chandle operators in expressions`
`20`	`20`	`parse_agg.chandle aggregates, like SUM(col1), AVG(col2), ...`
`21`	`21`	`parse_func.chandle functions, table.column and column identifiers`
`22`	`22`	`parse_node.ccreate nodes for various structures`
`23`	`23`	`parse_target.chandle the result list of the query`
`24`	`24`	`parse_relation.c support routines for tables and column handling`
`25`		`-parse_type.csupport routines for type handling`
	`25`	`+parse_type.csupport routines fordatatype handling`
`26`	`26`	`parse_utilcmd.cparse analysis for utility commands (done at execution time)`

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -1,14 +1,14 @@`
`1`		`-$PostgreSQL: pgsql/src/backend/utils/mmgr/README,v 1.12 2008/03/20 17:55:15 momjian Exp $`
	`1`	`+$PostgreSQL: pgsql/src/backend/utils/mmgr/README,v 1.13 2008/04/09 00:55:30 momjian Exp $`
`2`	`2`
`3`	`3`	`Notes About Memory Allocation Redesign`
`4`	`4`	`======================================`
`5`	`5`
`6`	`6`	`Up through version 7.0, Postgres had serious problems with memory leakage`
`7`	`7`	`during large queries that process a lot of pass-by-reference data. There`
`8`		`-was no provision for recycling memory until end of query. Thisneeds to be`
`9`		`-fixed, even more so with the advent of TOAST which willallow very large`
	`8`	`+was no provision for recycling memory until end of query. Thisneeded to be`
	`9`	`+fixed, even more so with the advent of TOAST which willallowed very large`
`10`	`10`	`chunks of data to be passed around in the system. This document describes`
`11`		`-the new memory managementplan implemented in 7.1.`
	`11`	`+the new memory managementsystem implemented in 7.1.`
`12`	`12`
`13`	`13`
`14`	`14`	`Background`

Comments

(0)