[COMMITTERS] pgloader - pgloader: Handle more nicely connection errors - from python
Log Message: --- Handle more nicely connection errors - from python stacktrace to ERROR message Modified Files: -- pgloader: pgloader.py (r1.27 -> r1.28) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgloader/pgloader/pgloader.py.diff?r1=1.27&r2=1.28) pgloader/pgloader: db.py (r1.14 -> r1.15) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgloader/pgloader/pgloader/db.py.diff?r1=1.14&r2=1.15) pgloader.py (r1.35 -> r1.36) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgloader/pgloader/pgloader/pgloader.py.diff?r1=1.35&r2=1.36) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Changed the way symbols are defined in C in INFORMIX mode.
Log Message: --- Changed the way symbols are defined in C in INFORMIX mode. Modified Files: -- pgsql/src/interfaces/ecpg: ChangeLog (r1.372 -> r1.373) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/ChangeLog?r1=1.372&r2=1.373) pgsql/src/interfaces/ecpg/include: datetime.h (r1.14 -> r1.15) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/include/datetime.h?r1=1.14&r2=1.15) decimal.h (r1.16 -> r1.17) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/include/decimal.h?r1=1.16&r2=1.17) ecpg_informix.h (r1.20 -> r1.21) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/include/ecpg_informix.h?r1=1.20&r2=1.21) pgsql/src/interfaces/ecpg/preproc: pgc.l (r1.161 -> r1.162) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/pgc.l?r1=1.161&r2=1.162) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Changed the way symbols are defined in C in INFORMIX mode.
Log Message: --- Changed the way symbols are defined in C in INFORMIX mode. Added SQLSTATE macro closing bug #3961. EXECUTE can return NOT FOUND so it should be checked here too. Tags: REL8_3_STABLE Modified Files: -- pgsql/src/interfaces/ecpg: ChangeLog (r1.370 -> r1.370.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/ChangeLog?r1=1.370&r2=1.370.2.1) pgsql/src/interfaces/ecpg/include: datetime.h (r1.12 -> r1.12.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/include/datetime.h?r1=1.12&r2=1.12.4.1) decimal.h (r1.14 -> r1.14.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/include/decimal.h?r1=1.14&r2=1.14.4.1) ecpg_informix.h (r1.18 -> r1.18.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/include/ecpg_informix.h?r1=1.18&r2=1.18.4.1) ecpglib.h (r1.74 -> r1.74.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/include/ecpglib.h?r1=1.74&r2=1.74.2.1) pgsql/src/interfaces/ecpg/preproc: pgc.l (r1.159 -> r1.159.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/pgc.l?r1=1.159&r2=1.159.2.1) preproc.y (r1.359 -> r1.359.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/preproc.y?r1=1.359&r2=1.359.2.1) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgrpm - pgrpm: 0.1.7
Log Message: --- 0.1.7 Modified Files: -- pgrpm: Makefile (r1.29 -> r1.30) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgrpm/pgrpm/Makefile.diff?r1=1.29&r2=1.30) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgrpm - pgrpm: - update changelog
Log Message: --- - update changelog Modified Files: -- pgrpm: ChangeLog (r1.10 -> r1.11) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgrpm/pgrpm/ChangeLog.diff?r1=1.10&r2=1.11) ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [COMMITTERS] pgsql: Changed the way symbols are defined in C in INFORMIX mode.
[EMAIL PROTECTED] (Michael Meskes) writes: > Log Message: > --- > Changed the way symbols are defined in C in INFORMIX mode. Not sure which patch caused it, but several of the buildfarm members are now failing on ecpg. regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Fixed conflicting commit.
Log Message: --- Fixed conflicting commit. Tags: REL8_3_STABLE Modified Files: -- pgsql/src/interfaces/ecpg/preproc: pgc.l (r1.159.2.1 -> r1.159.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/pgc.l?r1=1.159.2.1&r2=1.159.2.2) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Remove ancient restriction that LIMIT/OFFSET can't contain a
Log Message: --- Remove ancient restriction that LIMIT/OFFSET can't contain a sub-select. This was probably protecting some implementation limitation when it was put in, but as far as I can tell the planner and executor have no such assumption anymore; the case seems to work fine. Per a gripe from Grzegorz Jaskiewicz. Modified Files: -- pgsql/src/backend/parser: parse_clause.c (r1.168 -> r1.169) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_clause.c?r1=1.168&r2=1.169) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Updated expected result for regression test.
Log Message: --- Updated expected result for regression test. Tags: REL8_3_STABLE Modified Files: -- pgsql/src/interfaces/ecpg/test/expected: thread-prep.c (r1.4 -> r1.4.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/test/expected/thread-prep.c?r1=1.4&r2=1.4.2.1) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [COMMITTERS] pgsql: Changed the way symbols are defined in C in INFORMIX mode.
On Fri, Feb 15, 2008 at 10:49:32AM -0500, Tom Lane wrote: > [EMAIL PROTECTED] (Michael Meskes) writes: > > Log Message: > > --- > > Changed the way symbols are defined in C in INFORMIX mode. > > Not sure which patch caused it, but several of the buildfarm members > are now failing on ecpg. Strange, there was a CVS conflict in the file and somehow this made it into CVS. Frankly I have no idea how this happened, but it should be fixed now. Thanks. Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED] Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgd - pgd: Imported Sources
Update of /cvsroot/pgd/pgd In directory pgfoundry.org:/tmp/cvs-serv57088 Log Message: Initial import Status: Vendor Tag: nietsnie Release Tags: initial N pgd/pgd/Dynamic.d N pgd/pgd/Static.d N pgd/CVSROOT/checkoutlist N pgd/CVSROOT/commitinfo N pgd/CVSROOT/config N pgd/CVSROOT/cvswrappers N pgd/CVSROOT/editinfo N pgd/CVSROOT/loginfo N pgd/CVSROOT/modules N pgd/CVSROOT/notify N pgd/CVSROOT/rcsinfo N pgd/CVSROOT/taginfo N pgd/CVSROOT/verifymsg No conflicts created by this import ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [COMMITTERS] pgsql: Sync our regex code with upstream changes since last time we did
Andrew Dunstan wrote: > > > Tom Lane wrote: >> Note that I didn't make any effort to duplicate a lot of cosmetic changes >> that they made to bring their copy into line with their own style >> guidelines, such as adding braces around single-line IF bodies. Most of >> those we either had done already (such as ANSI-fication of function headers) >> or there is no point because pgindent would undo the change anyway. > > Not objecting, but IIRC we disabled the pgindent code that removes > braces around single line (or rather statement) IF bodies several years > ago. Yeah, we did, because it was removing the braces around PG_TRY() constructs. -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] pgsql: Allow AS to be omitted when specifying an output column name in
Log Message: --- Allow AS to be omitted when specifying an output column name in SELECT (or RETURNING), but only when the output name is not any SQL keyword. This seems as close as we can get to the standard's syntax without a great deal of thrashing. Original patch by Hiroshi Saito, amended by me. Modified Files: -- pgsql/doc/src/sgml: queries.sgml (r1.44 -> r1.45) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/queries.sgml?r1=1.44&r2=1.45) sql.sgml (r1.46 -> r1.47) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/sql.sgml?r1=1.46&r2=1.47) pgsql/doc/src/sgml/ref: delete.sgml (r1.32 -> r1.33) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/delete.sgml?r1=1.32&r2=1.33) insert.sgml (r1.35 -> r1.36) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/insert.sgml?r1=1.35&r2=1.36) select.sgml (r1.102 -> r1.103) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/select.sgml?r1=1.102&r2=1.103) select_into.sgml (r1.39 -> r1.40) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/select_into.sgml?r1=1.39&r2=1.40) update.sgml (r1.45 -> r1.46) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/update.sgml?r1=1.45&r2=1.46) pgsql/src/backend/parser: gram.y (r2.606 -> r2.607) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y?r1=2.606&r2=2.607) pgsql/src/interfaces/ecpg/preproc: preproc.y (r1.360 -> r1.361) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/preproc/preproc.y?r1=1.360&r2=1.361) pgsql/src/test/regress/expected: plpgsql.out (r1.58 -> r1.59) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/plpgsql.out?r1=1.58&r2=1.59) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgloader - pgloader: FIX end-of-file boundary checking
Log Message: --- FIX end-of-file boundary checking Modified Files: -- pgloader/pgloader: reader.py (r1.16 -> r1.17) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgloader/pgloader/pgloader/reader.py.diff?r1=1.16&r2=1.17) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgloader - pgloader: Synchronize threads starts and ends with an Event
Log Message: --- Synchronize threads starts and ends with an Event Modified Files: -- pgloader: pgloader.py (r1.28 -> r1.29) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgloader/pgloader/pgloader.py.diff?r1=1.28&r2=1.29) pgloader/pgloader: pgloader.py (r1.36 -> r1.37) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgloader/pgloader/pgloader/pgloader.py.diff?r1=1.36&r2=1.37) tools.py (r1.11 -> r1.12) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgloader/pgloader/pgloader/tools.py.diff?r1=1.11&r2=1.12) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
