[COMMITTERS] bizgres - bizgres: New Directory

Update of /cvsroot/bizgres/bizgres/postgresql/src/backend/access/bitmap In directory pgfoundry.org:/tmp/cvs-serv42163/backend/access/bitmap Log Message: Directory /cvsroot/bizgres/bizgres/postgresql/src/backend/access/bitmap added to the repository ---(end of broadcast)-

[COMMITTERS] bizgres - bizgres: Bug fix.

Log Message: --- Bug fix. COPY parsing failed to parse the first table attribute when it's not the first data field in the row. Modified Files: -- bizgres/postgresql/src/backend/commands: copy.c (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bi

[COMMITTERS] bizgres - bizgres: Updated release entry with loader revisions.

Log Message: --- Updated release entry with loader revisions. Modified Files: -- bizgres: release.txt (r1.12 -> r1.13) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/release.txt.diff?r1=1.12&r2=1.13) ---(end of broadca

[COMMITTERS] bizgres - bizgres: Command result clean up added.

Log Message: --- Command result clean up added. Modified Files: -- bizgres/loader/src/native/com/deepgreen/loader: lipqcmd.c (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/loader/src/native/com/deepgreen/loader/lipqcmd.c.diff?r1

[COMMITTERS] pgsql: Another try at the inlined MIPS spinlock code.

Log Message: --- Another try at the inlined MIPS spinlock code. Can't test this myself, but for sure it's not any more broken than the prior version. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/include/storage: s_lock.h (r1.133.4.1 -> r1.133.4.2)

[COMMITTERS] pgsql: Another try at the inlined MIPS spinlock code.

Log Message: --- Another try at the inlined MIPS spinlock code. Can't test this myself, but for sure it's not any more broken than the prior version. Modified Files: -- pgsql/src/include/storage: s_lock.h (r1.136 -> r1.137) (http://developer.postgresql.org

[COMMITTERS] bizgres - bizgres: Allowing the full 8 bit character set (LATIN1) to be

Log Message: --- Allowing the full 8 bit character set (LATIN1) to be used as delimiters, nulls, or escapes. Also added a test to see if the COPY command is accepted by the backend before starting to send data. Modified Files: -- bizgres/loader/src/com/deepgreen/loader:

[COMMITTERS] pgsql: Add: > o Issue a warning if a change-on-restart-only

Log Message: --- Add: > o Issue a warning if a change-on-restart-only postgresql.conf value > is modified and the server config files are reloaded > o Mark change-on-restart-only values in postgresql.conf 205a209 > o Fix SELECT '0.01 years'::interval, '0.01 month

[COMMITTERS] pgsql: Back-patch fixes for problems with VACUUM destroying t_ctid

Log Message: --- Back-patch fixes for problems with VACUUM destroying t_ctid chains too soon, and with insufficient paranoia in code that follows t_ctid links. This patch covers the 7.3 branch. Tags: REL7_3_STABLE Modified Files: -- pgsql/src/backend/access/heap:

[COMMITTERS] pgsql: Add description and item: > > Currently, while \e saves a

Log Message: --- Add description and item: > > Currently, while \e saves a single query as one entry, interactive > queries are saved one line at a time. Ideally all queries > whould be saved like \e does. > > o Allow multi-line column values to align in th

[COMMITTERS] pgsql: Update based on user comments: < in PL/PgSQL is to use

Log Message: --- Update based on user comments: < in PL/PgSQL is to use EXECUTE. > in PL/PgSQL is to use EXECUTE. One complexity is that a function > might itself drop and recreate dependent tables, causing it to > invalidate its own query plan. Modified Files: --

[COMMITTERS] pgsql: Update constraint_exclusion items: < inheritance, and allow it

Log Message: --- Update constraint_exclusion items: < inheritance, and allow it to work for UPDATE and DELETE queries > inheritance, allow it to work for UPDATE and DELETE queries, and allow > it to be used for all queries with little performance impact < * Allow constraint_eliminati

[COMMITTERS] pgsql: Remove completed items: < * -Allow limits on per-db/role

Log Message: --- Remove completed items: < * -Allow limits on per-db/role connections 43d41 < * -Prevent dropping user that still owns objects, or auto-drop the objects 49d46 < * -Add the client IP address and port to pg_stat_activity < * -Add session start time and last statement time to

[COMMITTERS] pgsql: Great TODO updates from Tom: < Currently SIGTERM of a backend

Log Message: --- Great TODO updates from Tom: < Currently SIGTERM of a backend can lead to lock table corruption. > Lock table corruption following SIGTERM of an individual backend > has been reported in 8.0. A possible cause was fixed in 8.1, but > it is unknown whether other pro

[COMMITTERS] pgsql: The idea of using _strncoll() on Windows doesn't work.

Log Message: --- The idea of using _strncoll() on Windows doesn't work. Revert to same code as we use on other platforms when encoding is not UTF8. Modified Files: -- pgsql/src/backend/utils/adt: varlena.c (r1.132 -> r1.133) (http://developer.postgresql.or

[COMMITTERS] pgsql: Back-port recent MIPS and M68K spinlock improvements to 8.0

Log Message: --- Back-port recent MIPS and M68K spinlock improvements to 8.0 branch. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/backend/storage/lmgr: s_lock.c (r1.35 -> r1.35.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/sto

[COMMITTERS] pgsql: Adjust m68k spinlock code to avoid duplicate in-line and

Log Message: --- Adjust m68k spinlock code to avoid duplicate in-line and not-in-line definitions on recent Linux systems, per Martin Pitt. Modified Files: -- pgsql/src/backend/storage/lmgr: s_lock.c (r1.37 -> r1.38) (http://developer.postgresql.org/cvsweb.