[COMMITTERS] bizgres - bizgres: Tagged version string.

2006-03-24 Thread User Llonergan
Log Message: --- Tagged version string. Modified Files: -- bizgres/postgresql: configure (r1.1.1.3.2.1 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/postgresql/configure.diff?r1=1.1.1.3.2.1&r2=1.3) configure.in (r1.1.1.3.2.1

[COMMITTERS] bizgres - bizgres: Includes: 1.

2006-03-24 Thread User Aparashar
Log Message: --- Includes: 1. Resolution of the copy issues on table that alerady has bitmap index. 2. Query run is fine for Bitmap And. Jie Modified Files: -- bizgres/postgresql/src/backend/access/bitmap: Makefile (r1.1 -> r1.2) (http://cvs.pgfoundry.org

[COMMITTERS] pgsql: Comments in IndexBuildHeapScan describe the indexing of

2006-03-24 Thread Tom Lane
Log Message: --- Comments in IndexBuildHeapScan describe the indexing of recently-dead tuples as needed "to keep VACUUM from complaining", but actually there is a more compelling reason to do it: failure to do so violates MVCC semantics. This is because a pre-existing serializable transacti

[COMMITTERS] pgsql: Comments in IndexBuildHeapScan describe the indexing of

2006-03-24 Thread Tom Lane
Log Message: --- Comments in IndexBuildHeapScan describe the indexing of recently-dead tuples as needed "to keep VACUUM from complaining", but actually there is a more compelling reason to do it: failure to do so violates MVCC semantics. This is because a pre-existing serializable transacti

[COMMITTERS] bizgres - bizgres: Introduce release Release-0_9_0

2006-03-24 Thread User Ksrikanth
Log Message: --- Introduce release Release-0_9_0 Modified Files: -- bizgres: release.txt (r1.17 -> r1.18) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/release.txt.diff?r1=1.17&r2=1.18) ---(end of broadcast)--