Log Message:
---
Re-ordered everything alpha order per Jim.
Removed e-mail marks, comments
Added estimated_rows,estimated_mb to tables, indexes
Other cleanup.
Modified Files:
--
newsysview/doc:
definition.txt (r1.4 -> r1.5)
(http://cvs.pgfoundry.org/cgi-bin
Log Message:
---
Add note about security view
Modified Files:
--
newsysview/doc:
definition.txt (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/newsysviews/newsysview/doc/definition.txt.diff?r1=1.3&r2=1.4)
---(end of bro
Log Message:
---
Forgot to ditch extra whitespace
Modified Files:
--
newsysview/doc:
definition.txt (r1.2 -> r1.3)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/newsysviews/newsysview/doc/definition.txt.diff?r1=1.2&r2=1.3)
---(end of
Log Message:
---
Add another round of back-and-forth
Modified Files:
--
newsysview/doc:
definition.txt (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/newsysviews/newsysview/doc/definition.txt.diff?r1=1.1&r2=1.2)
---(end
Log Message:
---
Initial start of definitions
Added Files:
---
newsysview/doc:
definition.txt (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/newsysviews/newsysview/doc/definition.txt?rev=1.1&content-type=text/x-cvsweb-markup)
---(e
Tom,
does this means that 'select 1 from foo where .' will not read heap
tuples (if index isn't loosy, of course) ?
On Mon, 28 Mar 2005, Tom Lane wrote:
Log Message:
---
First steps towards index scans with heap access decoupled from index
access: define new index access method function
Update of /cvsroot/newsysviews/newsysview/doc
In directory pgfoundry.org:/tmp/cvs-serv60895/doc
Log Message:
Directory /cvsroot/newsysviews/newsysview/doc added to the repository
---(end of broadcast)---
TIP 2: you can get off all lists at once wit
Update of /cvsroot/newsysviews/newsysview
In directory pgfoundry.org:/tmp/cvs-serv52128
Log Message:
Initial import
Status:
Vendor Tag: HEAD
Release Tags: initial
No conflicts created by this import
---(end of broadcast)--
Log Message:
---
Remove dead push/pop rollback code. Vadim once planned to implement
transaction rollback via UNDO but I think that's highly unlikely to
happen, so we may as well remove the stubs. (Someday we ought to
rip out the stub xxx_undo routines, too.) Per Alvaro.
Modified Files:
Log Message:
---
Rethink the order of expression preprocessing: eval_const_expressions
really ought to run before canonicalize_qual, because it can now produce
forms that canonicalize_qual knows how to improve (eg, NOT clauses).
Also, because eval_const_expressions already knows about flatt
Log Message:
---
First steps towards index scans with heap access decoupled from index
access: define new index access method functions 'amgetmulti' that can
fetch multiple TIDs per call. (The functions exist but are totally
untested as yet.) Since I was modifying pg_am anyway, remove the
Log Message:
---
Teach const-expression simplification to simplify boolean equality cases,
that is 'x = true' becomes 'x' and 'x = false' becomes 'NOT x'. This isn't
all that amazingly useful in itself, but it ensures that we will recognize
the different forms as being logically equivalent
Log Message:
---
Eliminate duplicate hasnulls bit testing in index tuple access, and
clean up itup.h a little bit.
Modified Files:
--
pgsql/src/backend/access/common:
indextuple.c (r1.73 -> r1.74)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backen
13 matches
Mail list logo