Re: [COMMITTERS] pgsql: Remove GIST concurrency limitations section.
On Sun, 3 Jul 2005, Neil Conway wrote: Bruce Momjian wrote: Remove GIST concurrency limitations section. - - 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. yes, this is the next step of our work on GiST. Call for support :) -Neil ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [email protected], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Improve outer-join-deduction logic to be able to propagate
Log Message: --- Improve outer-join-deduction logic to be able to propagate equalities through multiple join clauses. Modified Files: -- pgsql/src/backend/optimizer/path: pathkeys.c (r1.69 -> r1.70) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/pathkeys.c.diff?r1=1.69&r2=1.70) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Support cross compilation by compiling "zic" with a native
Log Message: --- Support cross compilation by compiling "zic" with a native compiler. This relies on the output of zic being platform independent, but that is currently the case. Modified Files: -- pgsql: configure (r1.441 -> r1.442) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.diff?r1=1.441&r2=1.442) configure.in (r1.414 -> r1.415) (http://developer.postgresql.org/cvsweb.cgi/pgsql/configure.in.diff?r1=1.414&r2=1.415) pgsql/doc/src/sgml: installation.sgml (r1.238 -> r1.239) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/installation.sgml.diff?r1=1.238&r2=1.239) pgsql/src: Makefile.global.in (r1.214 -> r1.215) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/Makefile.global.in.diff?r1=1.214&r2=1.215) pgsql/src/timezone: Makefile (r1.17 -> r1.18) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/timezone/Makefile.diff?r1=1.17&r2=1.18) ---(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: Don't try to constant-fold functions returning RECORD.
Log Message: --- Don't try to constant-fold functions returning RECORD. We were never able to do this before, but I had tried to make an exception for functions with OUT parameters. Michael Fuhr found one problem with it already, and I found another, which was it didn't work for strict functions with a NULL input. While both of these could be worked around, the probability that there are more gotchas seems high; I think prudence dictates just reverting to the former behavior for now. Accordingly, remove the kluge added to get_expr_result_type() for Michael's case. Modified Files: -- pgsql/src/backend/optimizer/util: clauses.c (r1.199 -> r1.200) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/util/clauses.c.diff?r1=1.199&r2=1.200) pgsql/src/backend/utils/fmgr: funcapi.c (r1.23 -> r1.24) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/fmgr/funcapi.c.diff?r1=1.23&r2=1.24) ---(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: Fix memory leak in plperl_hash_from_tuple(), per report from
Log Message: --- Fix memory leak in plperl_hash_from_tuple(), per report from Jean-Max Reymond. Modified Files: -- pgsql/src/pl/plperl: plperl.c (r1.78 -> r1.79) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/plperl.c.diff?r1=1.78&r2=1.79) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Fix memory leak in plperl_hash_from_tuple(), per report from
Log Message: --- Fix memory leak in plperl_hash_from_tuple(), per report from Jean-Max Reymond. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/pl/plperl: plperl.c (r1.67.4.1 -> r1.67.4.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/plperl.c.diff?r1=1.67.4.1&r2=1.67.4.2) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[COMMITTERS] newsysviews - newsysview: fix another mismatch between the rule deparse
Log Message: --- fix another mismatch between the rule deparse output and the regexps that try and break it apart. Modified Files: -- newsysview/sql: rules.sql (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/newsysviews/newsysview/sql/rules.sql.diff?r1=1.3&r2=1.4) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgbuildfarm - client-code: add comments to sample config making it
Log Message: --- add comments to sample config making it clear it is the server that sends email notifications. Modified Files: -- client-code: build-farm.conf (r1.10 -> r1.11) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbuildfarm/client-code/build-farm.conf.diff?r1=1.10&r2=1.11) ---(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
Re: [COMMITTERS] pgsql: Remove GIST concurrency limitations section.
- - 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. Chris ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Bruce, please apply this additional patch, that fixes the
Log Message: --- Bruce, please apply this additional patch, that fixes the auto-detection of AES. Now openssl.c just checks OpenSSL version. Whoever compiles newer OpenSSL without AES is on his own. Marko Kreen Modified Files: -- pgsql/contrib/pgcrypto: openssl.c (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/openssl.c.diff?r1=1.18&r2=1.19) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [COMMITTERS] pgsql: Remove GIST concurrency limitations section.
Christopher Kings-Lynne <[EMAIL PROTECTED]> writes: >> 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. Yeah, I agree. It'd be appropriate to mention the Aoki paper in TODO, but we don't normally document "stuff we'd like to do someday" as serious limitations. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Fix build break for out of tree (vpath) builds, induced by recent
Log Message: --- Fix build break for out of tree (vpath) builds, induced by recent zic changes. Modified Files: -- pgsql/src/timezone: Makefile (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/timezone/Makefile.diff?r1=1.18&r2=1.19) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [COMMITTERS] pgsql: Support cross compilation by compiling "zic"
Peter Eisentraut wrote: Support cross compilation by compiling "zic" with a native compiler. This relies on the output of zic being platform independent, but that is currently the case. This breaks out of tree (vpath) builds. Attached is a patch that fixes the problem -- committed to HEAD. -Neil Index: src/timezone/Makefile === RCS file: /var/lib/cvs/pgsql/src/timezone/Makefile,v retrieving revision 1.18 diff -c -r1.18 Makefile *** src/timezone/Makefile 3 Jul 2005 18:54:28 - 1.18 --- src/timezone/Makefile 4 Jul 2005 02:43:43 - *** *** 12,18 top_builddir = ../.. include $(top_builddir)/src/Makefile.global ! override CPPFLAGS := $(CPPFLAGS) # files to build into backend OBJS= localtime.o strftime.o pgtz.o --- 12,18 top_builddir = ../.. include $(top_builddir)/src/Makefile.global ! override CPPFLAGS := $(CPPFLAGS) -I$(srcdir) # files to build into backend OBJS= localtime.o strftime.o pgtz.o ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Update wording: < Currently, to protect against partial disk
Log Message: --- Update wording: < Currently, to protect against partial disk page writes, we write the > Currently, to protect against partial disk page writes, we write 877c877 < * Turn off after-change writes if fsync is disabled > * Turn off full page writes if fsync is disabled Modified Files: -- pgsql/doc: TODO (r1.1587 -> r1.1588) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1587&r2=1.1588) pgsql/doc/src/FAQ: TODO.html (r1.94 -> r1.95) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.94&r2=1.95) ---(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: Reverse this patch:
Log Message: --- Reverse this patch: --- > A quick look shows that when you use --with-libraries=/foo/bar the > generated link line for libraries says > > -L/foo/bar -lpq > > and it should probably be the other way around (as it is for the > executables). > > So I suspect we need some makefile tuning. You were correct. This patch fixes it. Jim C. Nasby Modified Files: -- pgsql/src: Makefile.shlib (r1.91 -> r1.92) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/Makefile.shlib.diff?r1=1.91&r2=1.92) ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [COMMITTERS] pgsql: Remove GIST concurrency limitations section.
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 Chris ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings Regards, Oleg _ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: [email protected], http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Arrange for the postmaster (and standalone backends, initdb, etc)
Log Message: --- Arrange for the postmaster (and standalone backends, initdb, etc) to chdir into PGDATA and subsequently use relative paths instead of absolute paths to access all files under PGDATA. This seems to give a small performance improvement, and it should make the system more robust against naive DBAs doing things like moving a database directory that has a live postmaster in it. Per recent discussion. Modified Files: -- pgsql/contrib/dbsize: dbsize.c (r1.18 -> r1.19) (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/dbsize/dbsize.c.diff?r1=1.18&r2=1.19) pgsql/src/backend/access/transam: slru.c (r1.25 -> r1.26) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/slru.c.diff?r1=1.25&r2=1.26) twophase.c (r1.7 -> r1.8) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/twophase.c.diff?r1=1.7&r2=1.8) xlog.c (r1.205 -> r1.206) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c.diff?r1=1.205&r2=1.206) pgsql/src/backend/bootstrap: bootstrap.c (r1.204 -> r1.205) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/bootstrap/bootstrap.c.diff?r1=1.204&r2=1.205) pgsql/src/backend/catalog: catalog.c (r1.61 -> r1.62) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/catalog.c.diff?r1=1.61&r2=1.62) pgsql/src/backend/commands: tablespace.c (r1.23 -> r1.24) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/tablespace.c.diff?r1=1.23&r2=1.24) pgsql/src/backend/libpq: be-secure.c (r1.57 -> r1.58) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/be-secure.c.diff?r1=1.57&r2=1.58) pgsql/src/backend/postmaster: pgarch.c (r1.16 -> r1.17) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/pgarch.c.diff?r1=1.16&r2=1.17) pgstat.c (r1.98 -> r1.99) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/pgstat.c.diff?r1=1.98&r2=1.99) postmaster.c (r1.457 -> r1.458) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c.diff?r1=1.457&r2=1.458) syslogger.c (r1.15 -> r1.16) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/syslogger.c.diff?r1=1.15&r2=1.16) pgsql/src/backend/storage/file: fd.c (r1.117 -> r1.118) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/file/fd.c.diff?r1=1.117&r2=1.118) pgsql/src/backend/storage/freespace: freespace.c (r1.45 -> r1.46) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/freespace/freespace.c.diff?r1=1.45&r2=1.46) pgsql/src/backend/storage/smgr: md.c (r1.116 -> r1.117) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/storage/smgr/md.c.diff?r1=1.116&r2=1.117) pgsql/src/backend/tcop: postgres.c (r1.451 -> r1.452) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c.diff?r1=1.451&r2=1.452) pgsql/src/backend/utils/adt: misc.c (r1.44 -> r1.45) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/misc.c.diff?r1=1.44&r2=1.45) pgsql/src/backend/utils/init: flatfiles.c (r1.11 -> r1.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/flatfiles.c.diff?r1=1.11&r2=1.12) globals.c (r1.95 -> r1.96) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/globals.c.diff?r1=1.95&r2=1.96) miscinit.c (r1.144 -> r1.145) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/miscinit.c.diff?r1=1.144&r2=1.145) postinit.c (r1.151 -> r1.152) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/init/postinit.c.diff?r1=1.151&r2=1.152) pgsql/src/backend/utils/misc: guc.c (r1.271 -> r1.272) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.271&r2=1.272) pgsql/src/bin/pg_resetxlog: pg_resetxlog.c (r1.34 -> r1.35) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_resetxlog/pg_resetxlog.c.diff?r1=1.34&r2=1.35) pgsql/src/include/access: slru.h (r1.11 -> r1.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/slru.h.diff?r1=1.11&r2=1.12) xlog.h (r1.65 -> r1.66) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/xlog.h.diff?r1=1.65&r2=1.66) xlog_internal.h (r1.8 -> r1.9) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/access/xlog_internal.h.diff?r1=1.8&r2=1.9) pgsql/src/include: miscadmin.h (r1.176 -> r1.177) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/includ
