[COMMITTERS] pgsql: int_aggregate's int_enum() doesn't work correctly with arrays

2005-04-22 Thread Tom Lane
Log Message: --- int_aggregate's int_enum() doesn't work correctly with arrays that aren't 1-D, so give an error message instead of failing. Per report from Ron Mayer. Tags: REL8_0_STABLE Modified Files: -- pgsql/contrib/intagg: int_aggregate.c (r1.13.4.3 ->

[COMMITTERS] pgsql: int_aggregate's int_enum() doesn't work correctly with arrays

2005-04-22 Thread Tom Lane
Log Message: --- int_aggregate's int_enum() doesn't work correctly with arrays that aren't 1-D, so give an error message instead of failing. Per report from Ron Mayer. Modified Files: -- pgsql/contrib/intagg: int_aggregate.c (r1.17 -> r1.18) (http://develo

[COMMITTERS] pgsql: int_aggregate's int_enum() doesn't work correctly with arrays

2005-04-22 Thread Tom Lane
Log Message: --- int_aggregate's int_enum() doesn't work correctly with arrays that aren't 1-D, so give an error message instead of failing. Per report from Ron Mayer. Tags: REL7_3_STABLE Modified Files: -- pgsql/contrib/intagg: int_aggregate.c (r1.6.2.3 -> r

[COMMITTERS] pgsql: int_aggregate's int_enum() doesn't work correctly with arrays

2005-04-22 Thread Tom Lane
Log Message: --- int_aggregate's int_enum() doesn't work correctly with arrays that aren't 1-D, so give an error message instead of failing. Per report from Ron Mayer. Tags: REL7_4_STABLE Modified Files: -- pgsql/contrib/intagg: int_aggregate.c (r1.11.4.3 ->

[COMMITTERS] pgsql: Fix typo: < Currently indexes do not have enough tuple tuple

2005-04-22 Thread Bruce Momjian
Log Message: --- Fix typo: < Currently indexes do not have enough tuple tuple visibility < information to allow data to be pulled from the index without < also accessing the heap. One way to allow this is to set a bit < to index tuples to indicate if a tuple is currently visible t

[COMMITTERS] pgsql: Updatable ResultSets need to check for an empty ResultSet because

2005-04-22 Thread Kris Jurka
Log Message: --- Updatable ResultSets need to check for an empty ResultSet because isBeforeFirst and isAfterLast both return false for an empty result so the checking to make sure the user is on a valid row wasn't working. Also don't allow an insert without specifying at least one column v

[COMMITTERS] pgsql: Release build 216.

2005-04-22 Thread Kris Jurka
Log Message: --- Release build 216. Tags: REL7_4_STABLE Modified Files: -- pgsql/src/interfaces/jdbc/org/postgresql: Driver.java.in (r1.36.2.6 -> r1.36.2.7) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/jdbc/org/postgresql/Driver.ja

[COMMITTERS] pgsql: Typo fix.

2005-04-22 Thread Bruce Momjian
Log Message: --- Typo fix. Alvaro. Modified Files: -- pgsql/doc/src/sgml/ref: select.sgml (r1.84 -> r1.85) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/select.sgml.diff?r1=1.84&r2=1.85) ---(end of broadcast)--

[COMMITTERS] tablelog - tablelog: test branching

2005-04-22 Thread User Kimhanse
Log Message: --- test branching Tags: tablelog_0_4_2_branch Added Files: --- tablelog: BRANCH_0_4_2.txt (r1.2.2.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/BRANCH_0_4_2.txt?rev=1.2.2.1&content-type=text/x-cvsweb-markup)

[COMMITTERS] pgsql: Turns out that my recent elimination of the 'redundant'

2005-04-22 Thread Tom Lane
Log Message: --- Turns out that my recent elimination of the 'redundant' flatten_andors() code in prepqual.c had a small drawback: the flatten_andors code was able to cope with deeply nested AND/OR structures (like 1 ORs in a row), whereas eval_const_expressions tends to recurse until i

[COMMITTERS] foot print for postgresq;

2005-04-22 Thread sandhya
hi, I am a newbie to Postgresql. I want to know the foot print of postgresql - server.   Is it possible to install only the postgreSql server  and use it?   regards sandhya.r  

[COMMITTERS] python - be: Make PyPgFunction inherit from PyPgObject(pg_proc entry).

2005-04-22 Thread James William Pye
Log Message: --- Make PyPgFunction inherit from PyPgObject(pg_proc entry). Move oid, old, new, and event to the Pull object, instead of passing in arguments. Update other dependencies as needed. Modified Files: -- be/include/pypg: call.h (r1.2 -> r1.3) (h

[COMMITTERS] pgsql: Add documentation stating how to determine if FSM settings are

2005-04-22 Thread Bruce Momjian
Log Message: --- Add documentation stating how to determine if FSM settings are too low --- look at a database-wide VACUUM VERBOSE. Modified Files: -- pgsql/doc/src/sgml: runtime.sgml (r1.314 -> r1.315) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/

[COMMITTERS] tablelog - tablelog: Using PGXS

2005-04-22 Thread User Kimhanse
Log Message: --- Using PGXS Modified Files: -- tablelog: Makefile (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/Makefile.diff?r1=1.1.1.1&r2=1.2) ---(end of broadcast)--- TI

[COMMITTERS] python - be: Make setup.py import friendly.

2005-04-22 Thread James William Pye
Log Message: --- Make setup.py import friendly. Also, make setup calculate installation directories at install time. Tweak as necessary in ldistutils. This allows 'be' to be configured and built prior to the installation of 'lo'. Modified Files: -- be: .cvsignore (

[COMMITTERS] python - be: Move some utility routines to tupledesc.c

2005-04-22 Thread James William Pye
Log Message: --- Move some utility routines to tupledesc.c Modified Files: -- be/include/pypg: utils.h (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/be/include/pypg/utils.h.diff?r1=1.2&r2=1.3) tupledesc.h (r1.3 -> r1.4)

[COMMITTERS] pgsql: Backpatch of LIMIT / FOR UPDATE behavior, but keep pre-7.3

2005-04-22 Thread Bruce Momjian
Log Message: --- Backpatch of LIMIT / FOR UPDATE behavior, but keep pre-7.3 mention in 8.0.X. Tags: REL8_0_STABLE Modified Files: -- pgsql/doc/src/sgml/ref: select.sgml (r1.80.4.1 -> r1.80.4.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src

[COMMITTERS] tablelog - tablelog: test branching

2005-04-22 Thread User Kimhanse
Log Message: --- test branching Removed Files: - tablelog: BRANCH_0_4_2.txt (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/BRANCH_0_4_2.txt) ---(end of broadcast)--- TIP 5: Have you checked ou

[COMMITTERS] tablelog - tablelog: Fix small warnings

2005-04-22 Thread User Kimhanse
Log Message: --- Fix small warnings Modified Files: -- tablelog: table_log_restore.c (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/table_log_restore.c.diff?r1=1.1&r2=1.2) ---(end of broadcast)

[COMMITTERS] tablelog - tablelog: test branching

2005-04-22 Thread User Kimhanse
Log Message: --- test branching Added Files: --- tablelog: BRANCH_0_5_0.txt (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/BRANCH_0_5_0.txt?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)-

[COMMITTERS] tablelog - tablelog: Split table_log.c into two files, logging vs.

2005-04-22 Thread User Kimhanse
Log Message: --- Split table_log.c into two files, logging vs. restoring Modified Files: -- tablelog: Makefile (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/Makefile.diff?r1=1.2&r2=1.3) table_log.c (r1.7 -> r1.8)

[COMMITTERS] pgsql: Fix bogus EXPLAIN display of rowcount estimates for BitmapAnd and

2005-04-22 Thread Tom Lane
Log Message: --- Fix bogus EXPLAIN display of rowcount estimates for BitmapAnd and BitmapOr nodes. Modified Files: -- pgsql/src/backend/optimizer/plan: createplan.c (r1.183 -> r1.184) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/p

[COMMITTERS] pgsql: Teach choose_bitmap_and() to actually be choosy --- that is, try

2005-04-22 Thread Tom Lane
Log Message: --- Teach choose_bitmap_and() to actually be choosy --- that is, try to make some estimate of which available indexes to AND together, rather than blindly taking 'em all. This could probably stand further improvement, but it seems to do OK in simple tests. Modified Files: ---

[COMMITTERS] tablelog - tablelog: Add simple tests

2005-04-22 Thread User Kimhanse
Log Message: --- Add simple tests Modified Files: -- tablelog: table_log.sql.in (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/table_log.sql.in.diff?r1=1.2&r2=1.3) table_log_init.sql (r1.1 -> r1.2) (http://cvs

[COMMITTERS] tablelog - tablelog: New Directory

2005-04-22 Thread User Kimhanse
Update of /cvsroot/tablelog/tablelog/test/benchmark In directory pgfoundry.org:/tmp/cvs-serv65773/benchmark Log Message: Directory /cvsroot/tablelog/tablelog/test/benchmark added to the repository ---(end of broadcast)--- TIP 8: explain analyze is

[COMMITTERS] python - be: Move the TIF_Repr into htup_repr.

2005-04-22 Thread James William Pye
Log Message: --- Move the TIF_Repr into htup_repr. The tif repr routine is no longer necessary as obj_repr will just use ts->typoutput(recordout), and it is unlikely for a need to externalize again. (Although, if that is not the case it will likely appear in heaptuple.c, instead of tif) Rem

[COMMITTERS] tablelog - tablelog: New Directory

2005-04-22 Thread User Kimhanse
Update of /cvsroot/tablelog/tablelog/test In directory pgfoundry.org:/tmp/cvs-serv65677/test Log Message: Directory /cvsroot/tablelog/tablelog/test added to the repository ---(end of broadcast)--- TIP 8: explain analyze is your friend

[COMMITTERS] pgsql: First cut at planner support for bitmap index scans.

2005-04-22 Thread Tom Lane
Log Message: --- First cut at planner support for bitmap index scans. Lots to do yet, but the code is basically working. Along the way, rewrite the entire approach to processing OR index conditions, and make it work in join cases for the first time ever. orindxpath.c is now basically obs

[COMMITTERS] tablelog - tablelog: test branching

2005-04-22 Thread User Kimhanse
Log Message: --- test branching Added Files: --- tablelog: BRANCH_0_4_2.txt (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/BRANCH_0_4_2.txt?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)-

[COMMITTERS] pgsql: When moveToCurrentRow is called and the current row is off the

2005-04-22 Thread Kris Jurka
Log Message: --- When moveToCurrentRow is called and the current row is off the end of the ResultSet we can't try to load that row because it doesn't exist and will throw an Exception. Reported by Prasanth. Tags: REL7_4_STABLE Modified Files: -- pgsql/src/interfaces/

[COMMITTERS] tablelog - tablelog: Prepare release 0.4.2, add description of

2005-04-22 Thread User Kimhanse
Log Message: --- Prepare release 0.4.2, add description of tabel_log_init to README Modified Files: -- tablelog: README.table_log (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/README.table_log.diff?r1=1.1.1.1&r2=1.2)

[COMMITTERS] tablelog - tablelog: Generate table_log.sql using Makefile.nocontrib

2005-04-22 Thread User Kimhanse
Log Message: --- Generate table_log.sql using Makefile.nocontrib Modified Files: -- tablelog: Makefile.nocontrib (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/Makefile.nocontrib.diff?r1=1.2&r2=1.3) --

[COMMITTERS] tablelog - tablelog: Add numbers to error messages

2005-04-22 Thread User Kimhanse
Log Message: --- Add numbers to error messages Modified Files: -- tablelog: table_log.c (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/table_log.c.diff?r1=1.6&r2=1.7) ---(end of broadcast)-

[COMMITTERS] pgsql: Update URL for TODO list.

2005-04-22 Thread Bruce Momjian
Log Message: --- Update URL for TODO list. Modified Files: -- pgsql/doc: TODO (r1.1502 -> r1.1503) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1502&r2=1.1503) pgsql/doc/src/FAQ: TODO.html (r1.9 -> r1.10) (http:/

[COMMITTERS] oledb - oledb: Report length of "char" fields as well.

2005-04-22 Thread User Shachar
Log Message: --- Report length of "char" fields as well. Modified Files: -- oledb: PgSess.cpp (r1.35 -> r1.36) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/oledb/oledb/PgSess.cpp.diff?r1=1.35&r2=1.36) ---(end of broadcast)--

[COMMITTERS] oledb - oledb: First attempt to solve the varchar length report bug

2005-04-22 Thread User Shachar
Log Message: --- First attempt to solve the varchar length report bug (#1000286) Modified Files: -- oledb: PgSess.cpp (r1.34 -> r1.35) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/oledb/oledb/PgSess.cpp.diff?r1=1.34&r2=1.35) TypeInfo.cpp (r1.15 -> r