[COMMITTERS] npgsql - Npgsql: 2008-09-03 Francisco Figueiredo Jr.
Log Message: --- 2008-09-03 Francisco Figueiredo Jr. <[EMAIL PROTECTED]> NpgsqlCommandBuilder.cs: Removed Gridnine patch as the permission to relicense to BSD couldn't be obtained. Modified Files: -- Npgsql/src/Npgsql: NpgsqlCommandBuilder.cs (r1.15 -> r1.16) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql/src/Npgsql/NpgsqlCommandBuilder.cs.diff?r1=1.15&r2=1.16) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] npgsql - Npgsql: 2007-09-03 Francisco Figueiredo Jr.
Log Message: --- 2007-09-03 Francisco Figueiredo Jr. <[EMAIL PROTECTED]> License.txt: Changed license from LGPL to BSD. Modified Files: -- Npgsql: LICENSE.txt (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql/LICENSE.txt.diff?r1=1.3&r2=1.4) ---(end of broadcast)--- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate
Re: [COMMITTERS] pgsql: Improve stylistic consistency of descriptions of built-in objects
Are there any SGML changes related to this? --- Tom Lane wrote: > Log Message: > --- > Improve stylistic consistency of descriptions of built-in objects by avoiding > initcap style --- the vast majority of the existing descriptions do not use > an initial cap. I didn't change places where the first word was all-cap. > > initdb not forced because this doesn't change any regression test results. > > Modified Files: > -- > pgsql/src/backend/snowball: > snowball.sql.in (r1.3 -> r1.4) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/snowball/snowball.sql.in?r1=1.3&r2=1.4) > snowball_func.sql.in (r1.1 -> r1.2) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/snowball/snowball_func.sql.in?r1=1.1&r2=1.2) > pgsql/src/include/catalog: > pg_database.h (r1.43 -> r1.44) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_database.h?r1=1.43&r2=1.44) > pg_language.h (r1.30 -> r1.31) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_language.h?r1=1.30&r2=1.31) > pg_namespace.h (r1.21 -> r1.22) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_namespace.h?r1=1.21&r2=1.22) > pg_proc.h (r1.466 -> r1.467) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_proc.h?r1=1.466&r2=1.467) > pg_ts_template.h (r1.1 -> r1.2) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_ts_template.h?r1=1.1&r2=1.2) > pg_type.h (r1.187 -> r1.188) > > (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_type.h?r1=1.187&r2=1.188) > > ---(end of broadcast)--- > TIP 6: explain analyze is your friend -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(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: Support SET FROM CURRENT in CREATE/ALTER FUNCTION, ALTER
Log Message: --- Support SET FROM CURRENT in CREATE/ALTER FUNCTION, ALTER DATABASE, ALTER ROLE. (Actually, it works as a plain statement too, but I didn't document that because it seems a bit useless.) Unify VariableResetStmt with VariableSetStmt, and clean up some ancient cruft in the representation of same. Modified Files: -- pgsql/doc/src/sgml/ref: alter_database.sgml (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_database.sgml?r1=1.19&r2=1.20) alter_function.sgml (r1.14 -> r1.15) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_function.sgml?r1=1.14&r2=1.15) alter_role.sgml (r1.8 -> r1.9) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_role.sgml?r1=1.8&r2=1.9) alter_user.sgml (r1.43 -> r1.44) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/alter_user.sgml?r1=1.43&r2=1.44) create_function.sgml (r1.76 -> r1.77) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/create_function.sgml?r1=1.76&r2=1.77) pgsql/src/backend/commands: dbcommands.c (r1.197 -> r1.198) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/dbcommands.c?r1=1.197&r2=1.198) functioncmds.c (r1.84 -> r1.85) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/functioncmds.c?r1=1.84&r2=1.85) user.c (r1.176 -> r1.177) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/user.c?r1=1.176&r2=1.177) pgsql/src/backend/nodes: copyfuncs.c (r1.381 -> r1.382) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/copyfuncs.c?r1=1.381&r2=1.382) equalfuncs.c (r1.312 -> r1.313) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/nodes/equalfuncs.c?r1=1.312&r2=1.313) pgsql/src/backend/parser: gram.y (r2.601 -> r2.602) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y?r1=2.601&r2=2.602) pgsql/src/backend/tcop: pquery.c (r1.116 -> r1.117) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/pquery.c?r1=1.116&r2=1.117) utility.c (r1.285 -> r1.286) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/utility.c?r1=1.285&r2=1.286) pgsql/src/backend/utils/misc: guc.c (r1.415 -> r1.416) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c?r1=1.415&r2=1.416) pgsql/src/include/nodes: nodes.h (r1.203 -> r1.204) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/nodes.h?r1=1.203&r2=1.204) parsenodes.h (r1.352 -> r1.353) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/parsenodes.h?r1=1.352&r2=1.353) pgsql/src/include/utils: guc.h (r1.84 -> r1.85) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/utils/guc.h?r1=1.84&r2=1.85) ---(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
Re: [COMMITTERS] pgsql: Improve stylistic consistency of descriptions of built-in objects
Bruce Momjian <[EMAIL PROTECTED]> writes: > Are there any SGML changes related to this? Don't think so --- what sort of changes have you got in mind? regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [COMMITTERS] pgsql: Improve stylistic consistency of descriptions of built-in objects
Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Are there any SGML changes related to this? > > Don't think so --- what sort of changes have you got in mind? >From textsearch.sgml: => \dFp+ Fulltext parser "pg_catalog.default" Method | Function | Description My question is whether there are any psql output examples in the SGML that will change. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(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
Re: [COMMITTERS] pgsql: Improve stylistic consistency of descriptions of built-in objects
Bruce Momjian <[EMAIL PROTECTED]> writes: > My question is whether there are any psql output examples in the SGML > that will change. Oh, not sure. It wouldn't be a significant change, but I guess it would be good for the examples to match exactly. I'll look. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pllolcode - tmp: Start killing off shift/reduce errors
Log Message: --- Start killing off shift/reduce errors Modified Files: -- tmp: gram.y (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolcode/tmp/gram.y.diff?r1=1.2&r2=1.3) ---(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] pllolcode - tmp: Getting closer -- now working on MEBBE
Log Message: --- Getting closer -- now working on MEBBE Modified Files: -- tmp: gram.y (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolcode/tmp/gram.y.diff?r1=1.3&r2=1.4) scan.l (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolcode/tmp/scan.l.diff?r1=1.2&r2=1.3) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Restrict tsearch config file base names to contain a-z, 0-9, and
Log Message: --- Restrict tsearch config file base names to contain a-z, 0-9, and underscore, instead of the initial policy of whatever isalpha() likes. Per discussion. Modified Files: -- pgsql/src/backend/tsearch: ts_utils.c (r1.3 -> r1.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tsearch/ts_utils.c?r1=1.3&r2=1.4) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Sync examples of psql \dF output with current CVS HEAD behavior.
Log Message: --- Sync examples of psql \dF output with current CVS HEAD behavior. Random other wordsmithing. Modified Files: -- pgsql/doc/src/sgml: textsearch.sgml (r1.15 -> r1.16) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/textsearch.sgml?r1=1.15&r2=1.16) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
