[COMMITTERS] pgsql: Adds some missing error handling to PGTYPESnumeric_div() in

Log Message: --- Adds some missing error handling to PGTYPESnumeric_div() in ecpg's pgtypeslib: (1) we need to check the return value of sub_abs() (2) we need to check the return value of 4 calls to digitbuf_alloc(). Per Coverity static analysis performed by EnterpriseDB. Modified Files:

[COMMITTERS] pgsql: Fix some minor infelicities in ecpg's pgtypeslib: (1) `pstr' must

Log Message: --- Fix some minor infelicities in ecpg's pgtypeslib: (1) `pstr' must be non-NULL in this function, so there is no need to check for it (2) we should check the return value of pgtypes_strdup(). Patch from Eric Astor at EnterpriseDB, with slight cleanup by myself, per a report f

[COMMITTERS] python - ex: Fix breakage cause by previous commit.

Log Message: --- Fix breakage cause by previous commit. The code keyword overloaded the global code. Just import it as another name for now. (Shouldn't be too expensive). Modified Files: -- ex/src: prime.py (r1.5 -> r1.6) (http://cvs.pgfoundry.org/cgi-bin/c

Re: [COMMITTERS] PgFoundry mailings

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Thu, 30 Jun 2005, Peter Eisentraut wrote: Why do we keep getting pgfoundry commit mailings sent to this list at irregular intervals? Can someone get this under control? I think this has been discussed before. The default is that the comm

[COMMITTERS] tablelog - tablelog: modified run.sh to use variable for psql change

Log Message: --- modified run.sh to use variable for psql change < to -f, because < will not work properly on windows Modified Files: -- tablelog/test/benchmark: run.sh (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/test/bench

[COMMITTERS] python - ex: Use 'code' instead of 'ec' to enhance clarity.

Log Message: --- Use 'code' instead of 'ec' to enhance clarity. (Also for coming checkin, to allow Postgres.exceptions.code.X) Modified Files: -- ex/src: prime.py (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/ex/src/prime.py.diff?r1=1.4

[COMMITTERS] tablelog - tablelog: small changes

Log Message: --- small changes Modified Files: -- tablelog: Makefile.nocontrib (r1.6 -> r1.7) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/Makefile.nocontrib.diff?r1=1.6&r2=1.7) tablelog/test/benchmark: run.sh (r1.2 -> r1.3)

[COMMITTERS] docbot - docbot: make output more nicely

Log Message: --- make output more nicely Modified Files: -- docbot: docbot.pl (r1.45 -> r1.46) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/docbot/docbot/docbot.pl.diff?r1=1.45&r2=1.46) ---(end of broadcast)-

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

Log Message: --- Introduce release Release-0_6_2 Modified Files: -- bizgres: release.txt (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/release.txt.diff?r1=1.7&r2=1.8) ---(end of broadcast)--

[COMMITTERS] bizgres - bizgres: Updates.

Log Message: --- Updates. Modified Files: -- bizgres/doc: DG_userguide.pdf (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/doc/DG_userguide.pdf.diff?r1=1.1&r2=1.2) README.txt (r1.1 -> r1.2) (http://cvs.pgfoundry.

[COMMITTERS] pgsql: Bug fixes for GiST crash recovery.

Log Message: --- Bug fixes for GiST crash recovery. - add forgotten check of lsn for insert completion - remove level of pages: hard to check in recovery - some cleanups Modified Files: -- pgsql/src/backend/access/gist: gist.c (r1.124 -> r1.125) (http://dev

[COMMITTERS] PgFoundry mailings

Why do we keep getting pgfoundry commit mailings sent to this list at irregular intervals? Can someone get this under control? ---(end of broadcast)--- TIP 8: explain analyze is your friend

[COMMITTERS] pgsql: Issue fatal error if no TCP/IP sockets could be created

Log Message: --- Issue fatal error if no TCP/IP sockets could be created Modified Files: -- pgsql/src/backend/postmaster: postmaster.c (r1.456 -> r1.457) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c.diff?r1=1.456&r2=

[COMMITTERS] python - be: Don't list_free_deep as it seems to be naughty here(?).

Log Message: --- Don't list_free_deep as it seems to be naughty here(?). Simplify Postgres.Execute. Modified Files: -- be/src: module.c (r1.17 -> r1.18) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/be/src/module.c.diff?r1=1.17&r2=1.18) query.

[COMMITTERS] pgsql: Minor ecpg tweak: the return value of calloc() is guaranteed to

Log Message: --- Minor ecpg tweak: the return value of calloc() is guaranteed to be NULL or zero-filled; therefore zero-filling it via memset() is pointless. (I think setting `errno' is probably a waste of cycles as well, but I haven't changed that.) Modified Files: -- pgsq

[COMMITTERS] pgsql: Warning cleanups for ecpg tests.

Log Message: --- Warning cleanups for ecpg tests. Avoid doing pointer arithmetic on void *, remove old-style function declarations, and mark a function "static". There are some remaining warnings, but this fixes most of them, anyway. Modified Files: -- pgsql/src/interfaces/

[COMMITTERS] pgsql: Fix ecpg's test/ Makefile for out-of-tree (vpath) builds.

Log Message: --- Fix ecpg's test/ Makefile for out-of-tree (vpath) builds. Modified Files: -- pgsql/src/interfaces/ecpg/test: Makefile (r1.49 -> r1.50) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/test/Makefile.diff?r1=1.49&r2=1.50)