[COMMITTERS] tablelog - tablelog: Adjust sleep-time
Log Message: --- Adjust sleep-time Modified Files: -- tablelog/test: sleep-1.sql (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/test/sleep-1.sql.diff?r1=1.1&r2=1.2) sleep-2.sql (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/test/sleep-2.sql.diff?r1=1.1&r2=1.2) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] tablelog - tablelog: Make test to see if it possible to break the
Log Message: --- Make test to see if it possible to break the logging by running a lot of concurrent transactions Added Files: --- tablelog/test: concurrent.pl (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/test/concurrent.pl?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[COMMITTERS] tablelog - tablelog: Explanation added to the test
Log Message: --- Explanation added to the test Modified Files: -- tablelog/test: concurrent.pl (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/test/concurrent.pl.diff?r1=1.1&r2=1.2) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] python - be: Boog squash.
Log Message: --- Boog squash. When the Query's context gets reset, out goes the TupleDesc of the tuplestore. Duplicate the descriptor in the PythonMemoryContext, so it doesn't segfault all over the floor. What a stain that leaves. Modified Files: -- be/src: query.c (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/be/src/query.c.diff?r1=1.8&r2=1.9) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] tablelog - tablelog: This problem shouldn't appear because of row-level
Log Message: --- This problem shouldn't appear because of row-level locking Modified Files: -- tablelog/test: concurrent.pl (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/tablelog/tablelog/test/concurrent.pl.diff?r1=1.2&r2=1.3) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [COMMITTERS] pgsql: Remove GIST concurrency limitations section.
Oleg Bartunov wrote: > On Mon, 4 Jul 2005, Christopher Kings-Lynne wrote: > > >> - > >> - The current implementation of GiST within > >> - PostgreSQL has some major limitations: > >> - GiST index access is not concurrent, and the > >> - GiST interface doesn't allow the development of > >> certain > >> - data types, such as digital trees (see papers by Aoki et al). > >> - > >> > >> AFAIK the GiST modifications suggested Aoki have not yet been implemented, > >> so this should not have been removed. > > > > I thought that was an extremely vague limitation and could easily be > > removed... It's like having a limitations section on btrees and have > > mentioning in passing that it can't do full text indexing or something. > > ok, it's sort of TODO Added to TODO: * Allow GIST indexes to create certain complex index types, like digital trees (see Aoki) -- Bruce Momjian| http://candle.pha.pa.us [email protected] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Update > * Allow GIST indexes to create certain complex index
Log Message: --- Update > * Allow GIST indexes to create certain complex index types, like digital > trees (see Aoki) > 783a787 > Modified Files: -- pgsql/doc: TODO (r1.1588 -> r1.1589) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1588&r2=1.1589) pgsql/doc/src/FAQ: TODO.html (r1.95 -> r1.96) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.95&r2=1.96) ---(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
[COMMITTERS] pgsql: Fix date_trunct for December dates that are in the next year,
Log Message:
---
Fix date_trunct for December dates that are in the next year, e.g.:
SELECT date_trunc('week', '2002-12-31'::date);
Backpatch to 8.0.X.
Per report from Nick Johnson.
Tags:
REL8_0_STABLE
Modified Files:
--
pgsql/src/backend/utils/adt:
timestamp.c (r1.117.4.2 -> r1.117.4.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/timestamp.c.diff?r1=1.117.4.2&r2=1.117.4.3)
---(end of broadcast)---
TIP 3: 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: Fix date_trunct for December dates that are in the next year,
Log Message:
---
Fix date_trunct for December dates that are in the next year, e.g.:
SELECT date_trunc('week', '2002-12-31'::date);
Backpatch to 8.0.X.
Per report from Nick Johnson.
Modified Files:
--
pgsql/src/backend/utils/adt:
timestamp.c (r1.128 -> r1.129)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/timestamp.c.diff?r1=1.128&r2=1.129)
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[COMMITTERS] pgsql: Backpatch to 8.0.X openssl portability fixes to pgcrypto.
Log Message: --- Backpatch to 8.0.X openssl portability fixes to pgcrypto. Tags: REL8_0_STABLE Modified Files: -- pgsql/contrib/pgcrypto: openssl.c (r1.13.4.1 -> r1.13.4.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/openssl.c.diff?r1=1.13.4.1&r2=1.13.4.2) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgbuildfarm - client-code: remove incorrect comment re crontab MAILTO -
Log Message: --- remove incorrect comment re crontab MAILTO - opened a new feature request for crontab notification Modified Files: -- client-code: build-farm.conf (r1.11 -> r1.12) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/build-farm.conf.diff?r1=1.11&r2=1.12) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Restructure TODO sections.
Log Message: --- Restructure TODO sections. Modified Files: -- pgsql/doc: TODO (r1.1589 -> r1.1590) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1589&r2=1.1590) pgsql/doc/src/FAQ: TODO.html (r1.96 -> r1.97) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.96&r2=1.97) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: More TODO list section restructuring.
Log Message: --- More TODO list section restructuring. Modified Files: -- pgsql/doc: TODO (r1.1590 -> r1.1591) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1590&r2=1.1591) pgsql/doc/src/FAQ: TODO.html (r1.97 -> r1.98) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.97&r2=1.98) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Fix compile if zic because it now doesn't use libpgport.
Log Message: --- Fix compile if zic because it now doesn't use libpgport. Modified Files: -- pgsql/src/timezone: pgtz.h (r1.12 -> r1.13) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/timezone/pgtz.h.diff?r1=1.12&r2=1.13) ---(end of broadcast)--- TIP 3: 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] pgbuildfarm - client-code: ignore files listed in cvsignore files -
Log Message: --- ignore files listed in cvsignore files - this will stop inappropriate triggering of vpath builds. Modified Files: -- client-code: run_build.pl (r1.30 -> r1.31) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/run_build.pl.diff?r1=1.30&r2=1.31) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: I made the patch that improved the performance of replace_text().
Log Message: --- I made the patch that improved the performance of replace_text(). The content of the patch is as follows: (1)Create shortcut when subtext was not found. (2)Stop using LEFT and RIGHT macro. In LEFT and RIGHT macro, TEXTPOS is executed by the same content as execution immediately before. The execution frequency of TEXTPOS can be reduced by using text_substring instead of LEFT and RIGHT macro. (3)Add appendStringInfoText, and use it instead of appendStringInfoString. There is an overhead of PG_TEXT_GET_STR when appendStringInfoString is executed by text type. This can be reduced by appendStringInfoText. (4)Reduce execution of TEXTDUP. The effect of the patch that I measured is as follows: - The Data for test was created by 'pgbench -i'. - Test SQL: select replace(aid, '9', 'A') from accounts; - Test results: Linux(CPU: Pentium III, Compiler option: -O2) original: 1.515s patched: 1.250s Atsushi Ogawa Modified Files: -- pgsql/src/backend/utils/adt: varlena.c (r1.123 -> r1.124) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varlena.c.diff?r1=1.123&r2=1.124) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: I have to admit that I got the case of the preprocessor symbol on
Log Message: --- I have to admit that I got the case of the preprocessor symbol on amd64 wrong. __AMD64__ is not defined, __amd64__ is. Christof Petig Modified Files: -- pgsql/src/interfaces/ecpg/ecpglib: execute.c (r1.41 -> r1.42) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/ecpglib/execute.c.diff?r1=1.41&r2=1.42) extern.h (r1.13 -> r1.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/ecpg/ecpglib/extern.h.diff?r1=1.13&r2=1.14) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: This patch allows the PL/Python module to do (SRF) functions.
Log Message: --- This patch allows the PL/Python module to do (SRF) functions. The patch was taken from the CVS version. I have modified the plpython.c file and have added a test sql script for testing the functionality. It was actually the script that was in the 8.0.3 version but have since been removed. In order to signal the end of a set, the called python function must simply return plpy.EndOfSet and the set would be returned. Gerrit van Dyk Added Files: --- pgsql/src/pl/plpython/sql: plpython_setof.sql (r1.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/sql/plpython_setof.sql?rev=1.1&content-type=text/x-cvsweb-markup) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: Restructure zic #define fprintf checks to use a NO_PGPORT macro
Log Message: --- Restructure zic #define fprintf checks to use a NO_PGPORT macro instead. Modified Files: -- pgsql/src/include: port.h (r1.76 -> r1.77) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/port.h.diff?r1=1.76&r2=1.77) pgsql/src/timezone: Makefile (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/timezone/Makefile.diff?r1=1.19&r2=1.20) pgtz.h (r1.13 -> r1.14) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/timezone/pgtz.h.diff?r1=1.13&r2=1.14) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgbuildfarm - client-code: add suppressible error message making
Log Message: --- add suppressible error message making defqault behavious suitable for crontab MAILTO. Modified Files: -- client-code: run_build.pl (r1.31 -> r1.32) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/run_build.pl.diff?r1=1.31&r2=1.32) ---(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
[COMMITTERS] pgbuildfarm - client-code: add a couple of comments.
Log Message: --- add a couple of comments. Modified Files: -- client-code: run_build.pl (r1.32 -> r1.33) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/run_build.pl.diff?r1=1.32&r2=1.33) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] docbot - docbot: - remember last question and answer it, if rtfm_please
Log Message: --- - remember last question and answer it, if rtfm_please has no answer Modified Files: -- docbot: docbot.pl (r1.46 -> r1.47) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/docbot/docbot/docbot.pl.diff?r1=1.46&r2=1.47) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
