gmane.comp.db.postgresql.announce http://blog.gmane.org/gmane.comp.db.postgresql.announce hourly 1 1901-01-01T00:00+00:00 Gmane http://gmane.org/img/gmane-25t.png http://gmane.org == PostgreSQL Weekly News - May 20 2012 == http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2041 <pre>== PostgreSQL Weekly News - May 20 2012 == The Call for Papers for PG.EU has begun. It will cover topics for PostgreSQL users, developers and contributors, as well as decision and policy makers. Talks should be in English or Czech. http://2012.pgconf.eu/ == PostgreSQL Product News == pgAdmin v1.16.0 Beta 1 is now available for testing in source from: http://www.postgresql.org/ftp/pgadmin3/release/v1.16.0-beta1/ PGXN Client 1.0.3 released. http://pgxnclient.projects.postgresql.org/ == PostgreSQL Jobs for May == http://archives.postgresql.org/pgsql-jobs/2012-05/threads.php == PostgreSQL Local == PGDay France will be in Lyon on June 7, 2012. http://www.pgday.fr PostgreSQL conference China 2012 will be on June 14-17, 2012 in Beijing. http://wiki.postgresql.org/wiki/Pgconfchina2012 PostgreSQL Session will be held on October 4th, 2012, in Paris, France. More information at: http://www.postgresql-sessions.org/en/4/ PostgreSQL Conference Europe 2012 will be in Prague, Czech Republic on October 23-26. The call for sponsors is open. http://2012.pgconf.eu/ == PostgreSQL in the News == Planet PostgreSQL: http://planet.postgresql.org/ PostgreSQL Weekly News is brought to you this week by David Fetter Submit news and announcements by Sunday at 3:00pm Pacific time. Please send English language ones to david&lt; at &gt;fetter.org, German language to pwn&lt; at &gt;pgug.de, Italian language to pwn&lt; at &gt;itpug.org. Spanish language to pwn&lt; at &gt;arpug.com.ar. == Reviews == == Applied Patches == Heikki Linnakangas pushed: - Update comments that became out-of-date with the PGXACT struct. When the "hot" members of PGPROC were split off to separate PGXACT structs, many PGPROC fields referred to in comments were moved to PGXACT, but the comments were neglected in the commit. Mostly this is just a search/replace of PGPROC with PGXACT, but the way the dummy PGPROC entries are created for prepared transactions changed more, making some of the comments totally bogus. Noah Misch http://git.postgresql.org/pg/commitdiff/9e4637bf89ef9fbc89a45dc4b421fa6740accd41 - Remove unnecessary pg_verifymbstr() calls from tsvector/query in functions. The input should've been validated well before it hits the input function. Doing so again is a waste of cycles. http://git.postgresql.org/pg/commitdiff/f15c2eae9c2f36830fae40935bd8cdcede4b75a0 - Fix bug in to_tsquery(). We were using memcpy() to copy to a possibly overlapping memory region, which is a no-no. Use memmove() instead. http://git.postgresql.org/pg/commitdiff/d2495f272cd164ff075bee5c4ce95aed11338a36 - Fix bug in freespace calculation in heap_multi_insert(). If the amount of freespace on page was less than the amount reserved by fillfactor, the calculation would underflow. This fixes bug #6643 reported by Tomonari Katsumata. http://git.postgresql.org/pg/commitdiff/6593c5b5dc39b179b1b7a3c947df2596af3e70c9 - Fix bug in gistRelocateBuildBuffersOnSplit(). When we create a temporary copy of the old node buffer, in stack, we mustn't leak that into any of the long-lived data structures. Before this patch, when we called gistPopItupFromNodeBuffer(), it got added to the array of "loaded buffers". After gistRelocateBuildBuffersOnSplit() exits, the pointer added to the loaded buffers array points to garbage. Often that goes unnotied, because when we go through the array of loaded buffers to unload them, buffers with a NULL pageBuffer are ignored, which can often happen by accident even if the pointer points to garbage. This patch fixes that by marking the temporary copy in stack explicitly as temporary, and refrain from adding buffers marked as temporary to the array of loaded buffers. While we're at it, initialize nodeBuffer-&gt;pageBlocknum to InvalidBlockNumber and improve comments a bit. This isn't strictly necessary, but makes debugging easier. http://git.postgresql.org/pg/commitdiff/1d27dcf5781ac7baeda0584fd016efc8eab718b3 Tom Lane pushed: - Force pgwin32_recv into nonblock mode when called from pgstat.c. This should get rid of the usage of pgwin32_waitforsinglesocket entirely, and perhaps thereby remove the race condition that's evidently still present on some versions of Windows. The previous arrangement was a bit unsafe anyway, since waiting at the recv() would not allow pgstat to notice postmaster death. http://git.postgresql.org/pg/commitdiff/f1ca51549e9e7045a2db95a61744334f1dbb4d64 - For testing purposes, reinsert a timeout in pgstat.c's wait call. Test results from buildfarm members mastodon/narwhal (Windows Server 2003) make it look like that platform just plain loses FD_READ events occasionally, and the only reason our previous coding seemed to work was that it timed out every couple of seconds and retried the whole operation. Try to verify this by reinserting a finite timeout into the pgstat loop. This isn't meant to be a permanent patch either, just to confirm or disprove a theory. http://git.postgresql.org/pg/commitdiff/d461d0502b6e20c6d4ec326ba2faec8212fd5dee - Assert that WaitLatchOrSocket callers cannot wait only for writability. Since we have chosen to report socket EOF and error conditions via the WL_SOCKET_READABLE flag bit, it's unsafe to wait only for WL_SOCKET_WRITEABLE; the caller would never be notified of the socket condition, and in some of these implementations WaitLatchOrSocket would busy-wait until something else happens. Add this restriction to the API specification, and add Asserts to check that callers don't try to do that. At some point we might want to consider adjusting the API to relax this restriction, but until we have an actual use case for waiting on a write-only socket, it seems premature to design a solution. http://git.postgresql.org/pg/commitdiff/e42a21b9e6c9b9e6346a34b62628d48ff2fc6ddf - Put back AC_REQUIRE([AC_STRUCT_TM]). The BSD-ish members of the buildfarm all seem to think removing this was a bad idea. It looks to me like it resulted in omitting the system header inclusion necessary to detect the fields of struct tm correctly. http://git.postgresql.org/pg/commitdiff/f667747b6d30c524c210501f5a2ca8e543a1bb67 - Revert "Add some temporary instrumentation to pgstat.c." This reverts commit 7d88bb73f755f7fb5d847ef2319c21076054fb0e. That instrumentation has served its purpose. http://git.postgresql.org/pg/commitdiff/5a2bb060121f574d6587e5fc6c7f1d4e3a759351 - In pgstat.c, use a timeout in WaitLatchOrSocket only on Windows. We have no need for a timeout here really, but some broken products from Redmond seem to lose FD_READ events occasionally, and waking up and retrying the recv() is the only known way to work around that. Perhaps somebody will be motivated to figure out a better answer here; but not I. http://git.postgresql.org/pg/commitdiff/9b63e9869ffaa4d6d3e8bf45086a765d8f310f1c - Improve error message for ALTER COLUMN TYPE coercion failure. Per recent discussion, the error message for this was actually a trifle inaccurate, since it said "cannot be cast" which might be incorrect. Adjust that wording, and add a HINT suggesting that a USING clause might be needed. http://git.postgresql.org/pg/commitdiff/488c6dd1708a2c4a9e9f307001f28c05c48651bd Peter Eisentraut pushed: - Remove unused AC_DEFINE symbols: ENABLE_DTRACE unused as of a7b7b07af340c73adee9959edf260695591a9496, HAVE_ERR_SET_MARK unused as of 4ed4b6c54e5fab24ab2624d80e26f7546edc88ad, HAVE_FCVT unused as of 4553e1d80f824291932cfde30aa24a76dd8f1941, HAVE_STRUCT_SOCKADDR_UN unused as of b4cea00a1fc9d2270bfe9aeeee44915378d5f733, HAVE_SYSCONF unused as of f83356c7f574bc69969f29dc7b430b286a0cd9f4, TM_IN_SYS_TIME never used, obsolescent per Autoconf documentation, http://git.postgresql.org/pg/commitdiff/ff4628f37a1e700d1fe716d0c271f68d8aa1e4ea - Remove stray nbsp character http://git.postgresql.org/pg/commitdiff/8afb026e57e746b8748d01798c0940ba02aaedde - Make xrefs to tables instead of assuming they appear below http://git.postgresql.org/pg/commitdiff/131b4d647388cb756e5aab1f1462c8b46125d89c - Remove whitespace from end of lines. pgindent and perltidy should clean up the rest. http://git.postgresql.org/pg/commitdiff/c8e086795a7ffc5244e03ffc2c92a3ae915a5055 - Fix a whitespace issue with the man pages. See 6ef24487967692604b07a4a54e71821a60fb729a for an explanation. This is the same for the new man pages. http://git.postgresql.org/pg/commitdiff/00b0c73f1f2b98a7d09de63aaa14d6498ac521ae - Change COLLATION keyword category. It was changed from unreserved to reserved as part of the COLLATION FOR syntax, but it turns out that type_func_name_keyword is sufficient. http://git.postgresql.org/pg/commitdiff/be6d1c88a4e6f563adac54483f3fc07ed8d8d99e - Update SQL features/conformance information to SQL:2011 http://git.postgresql.org/pg/commitdiff/939ec9b8a4cdd0c9ed9d1d85390d44942cd2edf6 - Update key words table for 9.2 http://git.postgresql.org/pg/commitdiff/4ad5cbedf6ea3186a286c61a164703b107f6a138 - file_fdw: Improve error message. The hint looked a bit confusing when there were no valid options to hint about. http://git.postgresql.org/pg/commitdiff/8402fab4112144a039157583b7e3368b8e31db3a - Realign some --help output to have better spacing between columns http://git.postgresql.org/pg/commitdiff/2273a50364cf4a098d7ee4b5aa7e88c5cc5777ad - Put back word that was mysteriously lost in man page conversion http://git.postgresql.org/pg/commitdiff/9c64f395578d98e6e988c378b6056ef787ff349d - Fix incorrect logic in JSON number lexer. Detectable by gcc -Wlogical-op. Add two regression test cases that would previously allow incorrect values to pass. http://git.postgresql.org/pg/commitdiff/f1f6737e154f9d00f1565fc08fd7ac677b380822 - Small cleanups of contrib --help output http://git.postgresql.org/pg/commitdiff/510860a6a5e4b66091353e7b0d619f71f6bec789 - Some reference page improvements. initdb: Add -T option. oid2name: Put options in some non-random order. pg_dump: Put --section option in the right place. And some additional markup and terminology improvements. http://git.postgresql.org/pg/commitdiff/fe2534e534c0572a71d6f0d2d51a2d058fc3524c Michael Meskes pushed: - Reworded sentence as suggested by Stephen Frost. http://git.postgresql.org/pg/commitdiff/c1ba858c6d49ae100f6e343932aa99c7a61e3f06 == Rejected Patches (for now) == No one was disappointed this week :-) == Pending Patches == Gilles Darold sent in another revision of the patch to add pg_is_in_backup() and pg_backup_start_time(). Fujii Masao sent in a patch which moves the existing calls of WalSndWakeup() out of a critical section and adds new call of WalSndWakeup() to XLogBackgroundFlush(). Alexander Shulgin sent in another revision of the patch to make libpq understand an RFC compliant URI connection string for PostgreSQL. Kyotaro HORIGUCHI sent in a patch to fix an infelicity in checkpointer. Stephen Frost sent in another revision of a patch to speed up some operations by pre-allocating ListCells. Robert Haas sent in a patch which provides some rough instrumentation for determining where palloc calls are coming from. Peter Eisentraut sent in a patch to add an aclcheck_error_type() function. ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> David Fetter 2012-05-21T06:08:55 PGXN Client 1.0.3 released http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2040 <pre>The PGXN Client version 1.0.3 has been released. The new release can deal with extensions whose Makefile is not directly available but is generated by the configure script; it also fixes a bug when the Makefile is not in the project root (ticket #12). Patches provided by Hitoshi Harada: thank you very much. The PGXN Client is a command line tool designed to interact with the PostgreSQL Extension Network allowing searching, compiling, installing, and removing extensions in a PostgreSQL installation or database. For further information about the program installation and usage please refer to the project homepage at &lt;http://pgxnclient.projects.postgresql.org/&gt;. Regards, </pre> Daniele Varrazzo 2012-05-19T20:53:17 Re: pgAdmin v.1.16.0 Beta 1 now available http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2039 <pre> Sorry, correct URL is http://www.postgresql.org/ftp/pgadmin3/release/v1.16.0-beta1/ </pre> Guillaume Lelarge 2012-05-16T18:54:25 pgAdmin v.1.16.0 Beta 1 now available http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2038 <pre>pgAdmin v1.16.0 Beta 1 is now available for testing in source from: http://www.postgresql.org/ftp/pgadmin3/release/v1.14.0-beta1/ Unfortunately, Windows and Mac OS X distributions aren't yet available. Nevertheless, you can still have it with the PostgreSQL 9.2 beta 1 one-click installer from: http://www.postgresql.org/download/snapshots/ We're still working on a visual tour. In the meantime, the list of new features is available in the changelog (http://www.pgadmin.org/development/changelog.php). Please download a copy to test, and report any issues to pgadmin-support&lt; at &gt;postgresql.org to help us prepare for our upcoming 1.16 final release. Regards. </pre> Guillaume Lelarge 2012-05-16T17:27:43 Call for Papers - PostgreSQL Conference Europe 2012 http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2037 <pre>PostgreSQL Conference Europe 2012 will be held on October 23-26 in Prague, The Czech Republic, at the Corinthia hotel. It will cover topics for PostgreSQL users, developers and contributors, as well as decision and policy makers. For more information about the conference, please see the website at http://2012.pgconf.eu/. We are now accepting proposals for talks. Please note that we are looking for talks in English and Czech. Each session will last 45 minutes, and may be on any topic related to PostgreSQL. Suggested topic areas include: * Developing applications for PostgreSQL * Administering large scale PostgreSQL installations * Case studies and/or success stories of PostgreSQL deployments * PostgreSQL tools and utilities * PostgreSQL hacking * Community &amp; user groups * Tuning the server * Migrating from other systems * Scaling/replication * Benchmarking &amp; hardware * PostgreSQL related products Of course, we're happy to receive proposals for talks on other PostgreSQL related topics as well. We also have a limited number of longer, 90-minute, slots available. Please indicate clearly in your submission if you wish to make a 90-minute talk. Finally, there will be a session of five minute lightning talks. A separate call for proposals will be made for them further on. The submission deadline is August 1st, 2012. Selected speakers will be notified before August 15th, 2012. Please submit your proposals by going to http://2012.pgconf.eu/callforpapers and following the instructions. If your proposal is in a non-english language, please include a single-sentence description of the presentation in English as well in the field for submission notes. The proposals will be considered by committee who will produce a schedule to be published nearer the conference date. All selected speakers will get free entry to the conference (excluding training sessions). We do not in general cover travel and accommodations for speakers, but may be able to do so in limited cases. If you require assistance with funding to be able to attend please make a note of this in the submission notes field. This call for papers is also available on the web at http://2012.pgconf.eu/callforpapers We look forward to hearing from you, and seeing you in Prague in October! ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> Magnus Hagander 2012-05-15T19:44:22 PostgreSQL 9.2 Beta 1 Now Available for Testing http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2036 <pre>The PostgreSQL Global Development Group announces the beta release of PostgreSQL 9.2, which will include major increases in performance and both vertical and horizontal scalability. The PostgreSQL Project asks all users to download and begin testing 9.2 Beta as soon as possible. Major performance and scalability advances in this version include: * Index-only scans, allowing users to avoid inefficient scans of base tables * Enhanced read-only workload scaling to 64 cores and over 300,000 queries per second * Improvements to data write speeds, including group commit * Reductions in CPU power consumption * Cascading replication, supporting geographically distributed standby databases PostgreSQL 9.2 will also offer many new features for application developers, including: * JSON data support, enabling hybrid document-relational databases * Range types, supporting new types of calendar, time-series and analytic applications * Multiple improvements to ALTER and other statements, easing runtime database updates For a full listing of the features in version 9.2 Beta, please see the release notes: http://www.postgresql.org/docs/devel/static/release-9-2.html We depend on our community to help test the next version in order to guarantee that it is high-performance and bug-free. Please download PostgreSQL 9.2 Beta and try it with your workloads and applications as soon as you can, and give feedback to the PostgreSQL developers. More information on how to test and report issues: http://www.postgresql.org/developer/beta Get PostgreSQL 9.2 beta, including binaries and installers for Windows, Linux and Mac from our download page: http://www.postgresql.org/download Full documentation of the new version is available online (http://www.postgresql.org/docs/devel/static), and also installs with PostgreSQL. ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> josh< at >postgresql.org 2012-05-14T22:48:49 == PostgreSQL Weekly News - May 13 2012 == http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2035 <pre>== PostgreSQL Weekly News - May 13 2012 == PostgreSQL Session will be held on October 4th, 2012, in Paris, France. More information at: http://www.postgresql-sessions.org/en/4/ == PostgreSQL Product News == AnySQL Maestro 12.5, an ODBC-based management tool which works with PostgreSQL, released. http://www.sqlmaestro.com/products/anysql/maestro/ pgXplorer, a GUI for postgres 8.4+, released. The code is open sourced under the ISC license and can be found on github at: https://github.com/davyjones/pgXplorer Postgres-XC 1.0beta2, a write-scalable multi-master symmetric cluster based on PostgreSQL, released. http://postgres-xc.sourceforge.net/docs/1_0/release-xc-1-0.html PL/Proxy 2.4, a database partitioning system implemented as a PL, released. http://pgfoundry.org/projects/plproxy/ SIDU 3.5 for PostgreSQL, a web-based tool for database administration, released. http://sidu.sf.net Version 1.25.1 of tail_n_mail, a Postgres log watcher program, released: http://bucardo.org/wiki/Tail_n_mail == PostgreSQL Jobs for May == http://archives.postgresql.org/pgsql-jobs/2012-05/threads.php == PostgreSQL Local == PGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of Ottawa. It will be preceded by two days of tutorials on 15-16 May 2012. http://www.pgcon.org/2012/ PGDay France will be in Lyon on June 7, 2012. http://www.pgday.fr PostgreSQL conference China 2012 will be on June 14-17, 2012 in Beijing. http://wiki.postgresql.org/wiki/Pgconfchina2012 PostgreSQL Conference Europe 2012 will be in Prague, Czech Republic on October 23-26. The call for sponsors is open. http://2012.pgconf.eu/ == PostgreSQL in the News == Planet PostgreSQL: http://planet.postgresql.org/ PostgreSQL Weekly News is brought to you this week by David Fetter Submit news and announcements by Sunday at 3:00pm Pacific time. Please send English language ones to david&lt; at &gt;fetter.org, German language to pwn&lt; at &gt;pgug.de, Italian language to pwn&lt; at &gt;itpug.org. Spanish language to pwn&lt; at &gt;arpug.com.ar. == Reviews == == Applied Patches == Magnus Hagander pushed: - Make "unexpected EOF" messages DEBUG1 unless in an open transaction. "Unexpected EOF on client connection" without an open transaction is mostly noise, so turn it into DEBUG1. With an open transaction it's still indicating a problem, so keep those as ERROR, and change the message to indicate that it happened in a transaction. http://git.postgresql.org/pg/commitdiff/916d589a10185bb30fc77923029d806f5907ab1e - Only attempt to show collations on servers &gt;= 9.1. Show a proper error message instead of a SQL error. Josh Kupershmidt http://git.postgresql.org/pg/commitdiff/f33c5d471ccdf33ac413d49b32a898eeab13538b Peter Eisentraut pushed: - Fix pg_config.h make rule. According to the Autoconf documentation, there should be a make rule pg_config.h: stamp-h so that with the right setup around this, a change in pg_config.h.in will trigger a rebuild of everything that depends on pg_config.h. But this doesn't always work, sometimes you need to run make twice to get everything up to date after a change of pg_config.h.in. The fix is to write the rule as pg_config.h: stamp-h ; instead (with an empty command instead of no command). This is what Automake-generated makefiles effectively do, so it seems safe to be on this side. It's not actually clear why this is (apparently) more correct. It's been posted to &lt;http://lists.gnu.org/archive/html/help-make/2012-04/msg00058.html&gt; without response so far. http://git.postgresql.org/pg/commitdiff/d7b2cd9d40e858778ca93b59383d280e510a01e7 - Remove strdup, strtol, strtoul from libpgport. These should not be needed anymore, at least after the recent port removals. So let's see whether we can do without them. http://git.postgresql.org/pg/commitdiff/3284e03d5d791e953e8c7eba25f1afb00c62e4a4 - Fix misleading comments. Josh Kupershmidt http://git.postgresql.org/pg/commitdiff/dcb2c5838183d3d305dbf713d4519d094f835b2f - Fix dependency tracking for src/port/%_srv.o files. Because they use their own compilation rule, they don't use the dependency tracking logic from Makefile.global. To make sure that dependency tracking works anyway for the *_srv.o files, depend on their *.o siblings as well, which do have proper dependencies. It's a hack that might fail someday if there is a *_srv.o without a corresponding *.o, but it works for now (and those would probably go into src/backend/port/ anyway). http://git.postgresql.org/pg/commitdiff/3420b241a7dbad8e5fe62395054bf8596f33d143 - Update config.guess and config.sub http://git.postgresql.org/pg/commitdiff/cf09230e1992a81e8e17441104d3c8a558abec04 - psql: Add variable to control keyword case in tab completion. This adds the variable COMP_KEYWORD_CASE, which controls in what case keywords are completed. This is partially to let users configure the change from commit 69f4f1c3576abc535871c6cfa95539e32a36120f, but it also offers more behaviors than were available before. http://git.postgresql.org/pg/commitdiff/db84ba65ab5c0ad0b34d68ab5a687bc5f4ca3ba6 - Tweak contrib --help output to match common style. Placeholders such as OPTION are typically kept in singular. http://git.postgresql.org/pg/commitdiff/081ca7a0d1991abe7ba6c3c219119335903c4111 - Update documentation to say that gmake check in contrib is supported http://git.postgresql.org/pg/commitdiff/4f696030ab1bbe950765d2687adb1d18a1358e15 - Split contrib documentation into extensions and programs. Create separate appendixes for contrib extensions and other server plugins on the one hand, and utility programs on the other. Recast the documentation of the latter as refentries, so that man pages are generated. http://git.postgresql.org/pg/commitdiff/1c882e07da553d792f479beb92b4729a4c0bd8de - Add make dependency so that postgres.bki is rebuilt in major version change. Every time since the current rule for postgres.bki was put in place when we change the major version, people complain that their tests fail in strange ways. This is because the version number in postgres.bki is not updated, because it has no dependency for that. And you can't even force the rebuild manually if you don't happen to know which file has the problem. Fix that now before it will happen again. The only remaining problem with switching major versions, as far as the regression tests are concerned, is that contrib needs to be rebuilt. But that's easily invoked, and in any case the failure modes are more friendly if you forget that. http://git.postgresql.org/pg/commitdiff/5d39807a008a5a73999477a7b3c21b2165fee549 - Python 2.2 is no longer supported. It was already on its last legs, and it turns out that it was accidentally broken in commit 89e850e6fda9e4e441712012abe971fe938d595a and no one cared. So remove the rest the support for it and update the documentation to indicate that Python 2.3 is now required. http://git.postgresql.org/pg/commitdiff/1d158d7f9841d7993f7b5990f311e3595db7960b - Whitespace cleanup http://git.postgresql.org/pg/commitdiff/d9bb75dd37ae1642392b8638c99bfeb9f9890c0a - PL/Python: Fix slicing support for result objects for Python 3. The old way of implementing slicing support by implementing PySequenceMethods.sq_slice no longer works in Python 3. You now have to implement PyMappingMethods.mp_subscript. Do this by simply proxying the call to the wrapped list of result dictionaries. Consolidate some of the subscripting regression tests. Jan Urbański http://git.postgresql.org/pg/commitdiff/a97207b6908f1d4a7d19b37b818367bb0171039f - PL/Python: Update incorrect comment. Jan Urbański http://git.postgresql.org/pg/commitdiff/1540d3bf4d405278533377ba81dbbf1c857eaec0 - Properly capitalize the TimeZone parameter. For better or worse, it is implemented in mixed case, so document it as such, at least in the main listing, like DateStyle. Josh Kupershmidt http://git.postgresql.org/pg/commitdiff/586d356bc5af1aa61f965f6ba1cbeb1533ec8c99 - PL/Python: Adjust the regression tests for Python 3.3. The string representation of ImportError changed. Remove printing that; it's not necessary for the test. The order in which members of a dict are printed changed. But this was always implementation-dependent, so we have just been lucky for a long time. Do the printing the hard way to ensure sorted order. http://git.postgresql.org/pg/commitdiff/2cfb1c6f77734db81b6e74bcae630f93b94f69be - Fix obsolescent C declaration syntax. gcc -Wextra/-Wold-style-declaration thinks that "inline" should go before the function return type. http://git.postgresql.org/pg/commitdiff/afe86a9e73b0d30f34dfdc196a6b52ce1306a95e - Remove unused AC_SUBST variables. These were apparently never used. The AC_SUBST was probably just added in a copy-and-paste manner. (The shell variables continue to be used inside configure. The change is just that we don't need them outside of configure.) http://git.postgresql.org/pg/commitdiff/7b85527eaee2cdcfc33d9f8c6c8e4a4908f7f58d - pg_ctl: Improve --help output. All other --help output has = signs between long options and their arguments, so do it here as well. http://git.postgresql.org/pg/commitdiff/2a7f6366409d54e9a61e2b7ba0277b7cdf15dbdc - Small punctuation editing of postgresql.conf.sample http://git.postgresql.org/pg/commitdiff/6bf1e7668dbdb5f97ae3b06f63bc0525be9d5387 - Remove leftovers of BeOS port. These should have been removed when the BeOS port was removed in 44f90212236bfb6fc1279e95dc8fa315104d964e. http://git.postgresql.org/pg/commitdiff/64f09ca38600ef0471683491f7735001b72c0f39 Tom Lane pushed: - Reduce idle power consumption of walwriter and checkpointer processes. This patch modifies the walwriter process so that, when it has not found anything useful to do for many consecutive wakeup cycles, it extends its sleep time to reduce the server's idle power consumption. It reverts to normal as soon as it's done any successful flushes. It's still true that during any async commit, backends check for completed, unflushed pages of WAL and signal the walwriter if there are any; so that in practice the walwriter can get awakened and returned to normal operation sooner than the sleep time might suggest. Also, improve the checkpointer so that it uses a latch and a computed delay time to not wake up at all except when it has something to do, replacing a previous hardcoded 0.5 sec wakeup cycle. This also is primarily useful for reducing the server's power consumption when idle. In passing, get rid of the dedicated latch for signaling the walwriter in favor of using its procLatch, since that comports better with possible generic signal handlers using that latch. Also, fix a pre-existing bug with failure to save/restore errno in walwriter's signal handlers. Peter Geoghegan, somewhat simplified by Tom http://git.postgresql.org/pg/commitdiff/5461564a9dfd73f12a21f2aff5d7b3678c7afc25 - Reduce idle power consumption of stats collector process. Latch-ify the stats collector, so that it does not need an arbitrary wakeup cycle to check for postmaster death. The incremental savings in idle power is pretty marginal, since we only had it waking every two seconds; but I believe that this patch may also improve the collector's performance under load, by reducing the number of kernel calls made per message when messages are arriving constantly (we now avoid a select/poll call except when we need to sleep). The change also reduces the time needed for a normal database shutdown on platforms where signals don't interrupt select(). http://git.postgresql.org/pg/commitdiff/49340037ee3ab46cb24144a86705e35f272c24d5 - Fix an issue in recent walwriter hibernation patch. Users of asynchronous-commit mode expect there to be a guaranteed maximum delay before an async commit's WAL records get flushed to disk. The original version of the walwriter hibernation patch broke that. Add an extra shared-memory flag to allow async commits to kick the walwriter out of hibernation mode, without adding any noticeable overhead in cases where no action is needed. http://git.postgresql.org/pg/commitdiff/acd4c7d58baf09fc278a0f8c1170fba2d56ccdd5 - Improve control logic for bgwriter hibernation mode. Commit 6d90eaaa89a007e0d365f49d6436f35d2392cfeb added a hibernation mode to the bgwriter to reduce the server's idle-power consumption. However, its interaction with the detailed behavior of BgBufferSync's feedback control loop wasn't very well thought out. That control loop depends primarily on the rate of buffer allocation, not the rate of buffer dirtying, so the hibernation mode has to be designed to operate only when no new buffer allocations are happening. Also, the check for whether the system is effectively idle was not quite right and would fail to detect a constant low level of activity, thus allowing the bgwriter to go into hibernation mode in a way that would let the cycle time vary quite a bit, possibly further confusing the feedback loop. To fix, move the wakeup support from MarkBufferDirty and SetBufferCommitInfoNeedsSave into StrategyGetBuffer, and prevent the bgwriter from entering hibernation mode unless no buffer allocations have happened recently. In addition, fix the delaying logic to remove the problem of possibly not responding to signals promptly, which was basically caused by trying to use the process latch's is_set flag for multiple purposes. I can't prove it but I'm suspicious that that hack was responsible for the intermittent "postmaster does not shut down" failures we've been seeing in the buildfarm lately. In any case it did nothing to improve the readability or robustness of the code. In passing, express the hibernation sleep time as a multiplier on BgWriterDelay, not a constant. I'm not sure whether there's any value in exposing the longer sleep time as an independently configurable setting, but we can at least make it act like this for little extra code. http://git.postgresql.org/pg/commitdiff/6308ba05a7a24b5137d97508300131ffa42051c2 - Further tweaking of nomenclature in checkpointer.c. Get rid of some more naming choices that only make sense if you know that this code used to be in the bgwriter, as well as some stray comments referencing the bgwriter. http://git.postgresql.org/pg/commitdiff/d3ae406f54d6f0d90b15f9e388025ef5a481e2c3 - Improve tests for postmaster death in auxiliary processes. In checkpointer and walwriter, avoid calling PostmasterIsAlive unless WaitLatch has reported WL_POSTMASTER_DEATH. This saves a kernel call per iteration of the process's outer loop, which is not all that much, but a cycle shaved is a cycle earned. I had already removed the unconditional PostmasterIsAlive calls in bgwriter and pgstat in previous patches, but forgot that WL_POSTMASTER_DEATH is supposed to be treated as untrustworthy (per comment in unix_latch.c); so adjust those two cases to match. There are a few other places where the same idea might be applied, but only after substantial code rearrangement, so I didn't bother. http://git.postgresql.org/pg/commitdiff/fd71421b0187de0e2bf76ff66b4a9433bd96c4a0 - Remove unportable use of SGML character-code entity. It'd be nice to be able to spell Jan Urbanski's name with the correct accent marks, but we haven't yet found a way that works in everybody's docs toolchain. This way definitely doesn't. http://git.postgresql.org/pg/commitdiff/47ce4c36a721b621b6b0ddcba9d02ccd0af5b3aa - Improve Windows implementation of WaitLatch/WaitLatchOrSocket. Ensure that signal handlers are serviced before this function returns. This should make the behavior more like Unix. Also, add some more error checking, and make some other cosmetic improvements. No back-patch since it's not clear whether this is fixing any live bug that would affect 9.1. I'm more concerned about 9.2 anyway given our considerable recent expansions in the usage of WaitLatch. http://git.postgresql.org/pg/commitdiff/8ebc908c575b3378c9d4096412d16d91d107311c - Fix Windows implementation of PGSemaphoreLock. The original coding failed to reset ImmediateInterruptOK before returning, which would potentially allow a subsequent query-cancel interrupt to be accepted at an unsafe point. This is a really nasty bug since it's so hard to predict the consequences, but they could be unpleasant. Also, ensure that signal handlers are serviced before this function returns, even if the semaphore is already set. This should make the behavior more like Unix. Back-patch to all supported versions. http://git.postgresql.org/pg/commitdiff/ada8fa08fc6cf5f199b6df935b4d0a730aaa4fec - Make WaitLatch's WL_POSTMASTER_DEATH result trustworthy; simplify callers. Per a suggestion from Peter Geoghegan, make WaitLatch responsible for verifying that the WL_POSTMASTER_DEATH bit it returns is truthful (by testing PostmasterIsAlive). Then simplify its callers, who no longer need to do that for themselves. Remove weasel wording about falsely-set result bits from WaitLatch's API contract. http://git.postgresql.org/pg/commitdiff/f40022f1adaeff85b01d98fea38cf5aa16814aa7 - Temporarily revert stats collector latch changes so we can ship beta1. This patch reverts commit 49340037ee3ab46cb24144a86705e35f272c24d5 and some follow-on tweaking in pgstat.c. While the basic scheme of latch-ifying the stats collector seems sound enough, it's failing on most Windows buildfarm members for unknown reasons, and there's no time left to debug that before 9.2beta1. Better to ship a beta version without this improvement. I hope to re-revert this once beta1 is out, though. http://git.postgresql.org/pg/commitdiff/cb2f2873d6b81ad7f0a9733ba738bfac0746fb7b - Tweak documentation wording to avoid "pdfendlink" failure. HEAD documentation was failing to build as US PDF for me, because a link to "CREATE CAST" was getting split across pages. Adjust wording to remove this rather gratuitous cross-reference. http://git.postgresql.org/pg/commitdiff/e3cdc1532caaec4652b41d1114c71aa3872a8f6f - Stamp 9.2beta1. http://git.postgresql.org/pg/commitdiff/f70fa835e08eee4cb2dc0f72d66cf633089c37e8 - Improve discussion of setting server parameters. Rewrite description of "include_if_exists" for clarity. Add subsection headings to make the structure of the page a little clearer. A couple other minor improvements too. Josh Kupershmidt and Tom Lane http://git.postgresql.org/pg/commitdiff/817ec1bc8227eb0d7f3bbb5725ea1de0ec73c1ea - Fix contrib/citext's upgrade script to handle array and domain cases. We previously recognized that citext wouldn't get marked as collatable during pg_upgrade from a pre-9.1 installation, and hacked its create-from-unpackaged script to manually perform the necessary catalog adjustments. However, we overlooked the fact that domains over citext, as well as the citext[] array type, need the same adjustments. Extend the script to handle those cases. Also, the documentation suggested that this was only an issue in pg_upgrade scenarios, which is quite wrong; loading any dump containing citext from a pre-9.1 server will also result in the type being wrongly marked. I approached the documentation problem by changing the 9.1.2 release note paragraphs about this issue, which is historically inaccurate. But it seems better than having the information scattered in multiple places, and leaving incorrect info in the 9.1.2 notes would be bad anyway. We'll still need to mention the issue again in the 9.1.4 notes, but perhaps they can just reference 9.1.2 for fix instructions. Per report from Evan Carroll. Back-patch into 9.1. http://git.postgresql.org/pg/commitdiff/63fecc91770f3d494b6fe993bdc198a9faf6fe2d - Cosmetic adjustments for postmaster's handling of checkpointer. Correct some comments, order some operations a bit more consistently. No functional changes. http://git.postgresql.org/pg/commitdiff/d0c231d13224621c2bd1e7e0466dd8000bdc1a02 - Update example of process titles shown by "ps". This example was quite old: it lacked the WAL writer and autovac launcher as well as the more recently added checkpointer. Linux "ps" seems to show slightly different stuff now too. http://git.postgresql.org/pg/commitdiff/f35ebd2aa1a2c5d99e859abed488b67c4e3694ff - Explain compatibility item about language names a bit more. Since we've got an "open items" list item about this, apparently some people are pretty worried about it. In passing remove a lot of trailing whitespace. http://git.postgresql.org/pg/commitdiff/a5985a96a82d96704984377a96c1945bcf914646 - Fix WaitLatchOrSocket to handle EOF on socket correctly. When using poll(), EOF on a socket is reported with the POLLHUP not POLLIN flag (at least on Linux). WaitLatchOrSocket failed to check this bit, causing it to go into a busy-wait loop if EOF occurs. We earlier fixed the same mistake in the test for the state of the postmaster_alive socket, but missed it for the caller-supplied socket. Fortunately, this error is new in 9.2, since 9.1 only had a select() based code path not a poll() based one. http://git.postgresql.org/pg/commitdiff/31ad6553646c81f3ce8fccf8aef1a1134a7864c7 - Avoid unnecessary process wakeups in the log collector. syslogger was coded to wake up once per second whether there was anything useful to do or not. As part of our campaign to reduce the server's idle power consumption, change it to use a latch for waiting. Now, in the absence of any data to log or any signals to service, it will only wake up at the programmed logfile rotation times (if any). http://git.postgresql.org/pg/commitdiff/398b240151708d7e971631875760ddbad3a63e0e - Fix bogus declaration of local variable. rc should be an int here, not a pgsocket. Fairly harmless as long as pgsocket is an integer type, but nonetheless wrong. Error introduced in commit 87091cb1f1ed914e2ddca424fa28f94fdf8461d2. http://git.postgresql.org/pg/commitdiff/fd350ef395b59e39bf419bd47e820b94dff23971 - Attempt to fix some issues in our Windows socket code. Make sure WaitLatchOrSocket regards FD_CLOSE as a read-ready condition. We might want to tweak this further, but it was surely wrong as-is. Make pgwin32_waitforsinglesocket detach its private event object from the passed socket before returning. I suspect that failure to do so leads to race conditions when other code (such as WaitLatchOrSocket) attaches a different event object to the same socket. Moreover, the existing coding meant that repeated calls to pgwin32_waitforsinglesocket would perform ResetEvent on an event actively connected to a socket, which is rumored to be an unsafe practice; the WSAEventSelect documentation appears to recommend against this, though it does not say not to do it in so many words. Also, uniformly use the coding pattern "WSAEventSelect(s, NULL, 0)" to detach events from sockets, rather than passing the event in the second parameter. The WSAEventSelect documentation says that the second parameter is ignored if the third is 0, so theoretically this should make no difference. However, elsewhere on the same reference page the use of NULL in this context is recommended, and I have found suggestions on the net that some versions of Windows have bugs with a non-NULL second parameter in this usage. Some other mostly-cosmetic cleanup, such as using the right one of WSAGetLastError and GetLastError for reporting errors from these functions. http://git.postgresql.org/pg/commitdiff/b85427f2276d02756b558c0024949305ea65aca5 - Re-revert stats collector latch changes. This reverts commit cb2f2873d6b81ad7f0a9733ba738bfac0746fb7b, restoring the latch-ified stats collector logic. We'll soon see if this works any better on the Windows buildfarm machines. http://git.postgresql.org/pg/commitdiff/966970ed636586b80739c0d21aec7561f0fafedd - Fix DROP TABLESPACE to unlink symlink when directory is not there. If the tablespace directory is missing entirely, we allow DROP TABLESPACE to go through, on the grounds that it should be possible to clean up the catalog entry in such a situation. However, we forgot that the pg_tblspc symlink might still be there. We should try to remove the symlink too (but not fail if it's no longer there), since not doing so can lead to weird behavior subsequently, as per report from Michael Nolan. There was some discussion of adding dependency links to prevent DROP TABLESPACE when the catalogs still contain references to the tablespace. That might be worth doing too, but it's an orthogonal question, and in any case wouldn't be back-patchable. Back-patch to 9.0, which is as far back as the logic looks like this. We could possibly do something similar in 8.x, but given the lack of reports I'm not sure it's worth the trouble, and anyway the case could not arise in the form the logic is meant to cover (namely, a post-DROP transaction rollback having resurrected the pg_tablespace entry after some or all of the filesystem infrastructure is gone). http://git.postgresql.org/pg/commitdiff/b8347138e94c4e712334508c460cbe0062d21e70 - Add some temporary instrumentation to pgstat.c. Log main-loop blocking events and the results of inquiry messages. This is to get some clarity as to what's happening on those Windows buildfarm members that still don't like the latch-ified stats collector. This bulks up the postmaster log a tad, so I won't leave it in place for long. http://git.postgresql.org/pg/commitdiff/7d88bb73f755f7fb5d847ef2319c21076054fb0e Bruce Momjian pushed: - Document how to find non-ASCII characters in the release notes. http://git.postgresql.org/pg/commitdiff/8b77e226fbf4834a03fcef2fa31aa85dac40c941 - Add another URL for HTML entity codes. http://git.postgresql.org/pg/commitdiff/773b5e0efa409d06113c3654f53da511de673a51 - Publish draft version of Postgres 9.2 release notes. http://git.postgresql.org/pg/commitdiff/668f959dcb7786654943d4726d1af07ad468a5be - Update 9.2 SSL release note links. http://git.postgresql.org/pg/commitdiff/e78cc624e87709e04960966c97a8d9f927f3d2f7 - Improve two 9.2 release note items. http://git.postgresql.org/pg/commitdiff/5d258fe90cbd6a0efd68e057697f85a1f961c42d - Release notes adjustments from Erik Rijkers http://git.postgresql.org/pg/commitdiff/1ee90397f498141abf0c77b4d3c9ea26babc072d - Remove URL that suggested numeric HTML entities. http://git.postgresql.org/pg/commitdiff/38cd7cc0bcd6fcbfa8942e28f6aee84ab9fbb651 - Another doc fix for HTML entities. http://git.postgresql.org/pg/commitdiff/d413efe9e14357577a3b7537784eb856ab6525ba - Update entitiy escapes docs; must be Latin1. http://git.postgresql.org/pg/commitdiff/77bfdb11d09a3adef1f9310201e1b2fe38ee47bd - 9.2 release note adjustments from Robert Haas. http://git.postgresql.org/pg/commitdiff/1908a6796a2e61e78c9a31807076746c34ea6a15 - Add 9.2 release note suggestions from Heikki Linnakangas, http://git.postgresql.org/pg/commitdiff/deb2c6e381e26b4e3c042b16990dd3821f6757b3 - New 9.2 SSL parameters are GUC, not libpq, per Magnus's observation. http://git.postgresql.org/pg/commitdiff/53216e3992665eda1570650f4047efa4202e7173 - 9.2 release note updates from Peter Geoghegan http://git.postgresql.org/pg/commitdiff/ffda90f3afe3f4db10127d2b853dfe4230720873 - Add comma after "Previously" as suggested by Josh Kupershmidt http://git.postgresql.org/pg/commitdiff/45f6fb2713feb21bc24fa907bad575008fd680ef - Merge visibility map crash-safety into index-only scan release note item, per Robert Haas. http://git.postgresql.org/pg/commitdiff/5428ff4af84e488c7f0629108cd12ff51125e09f - Update comment for 'name' data type to say 63 "bytes". Catalog version bump so everyone has the same comment for beta1. http://git.postgresql.org/pg/commitdiff/d2fe836cd28dbaff86f63b77da8d7ea0efa9a9c3 - Revert catalog bump; was post-beta1, and unnecessary. http://git.postgresql.org/pg/commitdiff/ee24de40018fe5b6f8dc015e56e41c7889622c33 - Update group commit release note item. http://git.postgresql.org/pg/commitdiff/d36eaa2167c4baaa654a19432035f47fdf6fbe7d Simon Riggs pushed: - Avoid xid error from age() function when run on Hot Standby http://git.postgresql.org/pg/commitdiff/5829387381d2e4edf84652bb5a712f6185860670 - Rename BgWriterCommLock to CheckpointerCommLock http://git.postgresql.org/pg/commitdiff/bbd3ec9dce0eca289c7a5d70fb754c8a7762180b - Rename BgWriterShmem/Request to CheckpointerShmem/Request http://git.postgresql.org/pg/commitdiff/8f28789bffd03e6d865039aff00c68db54d9f574 - Ensure age() returns a stable value rather than the latest value http://git.postgresql.org/pg/commitdiff/b06679e01244d33304b71a6a44c7cc86173617b3 - Remove extraneous #include "storage/proc.h" http://git.postgresql.org/pg/commitdiff/b762e8f50b3edefc0b8597dda46a18dc5e22b056 - Ensure backwards compatibility for GetStableLatestTransactionId() http://git.postgresql.org/pg/commitdiff/867540b49cd248ea867cfcf04d3dbb2ba4f506b8 Joe Conway pushed: - PL/pgSQL RETURN NEXT was leaking converted tuples, causing out of memory when looping through large numbers of rows. Flag the converted tuples to be freed. Complaint and patch by Joe. http://git.postgresql.org/pg/commitdiff/b58bacdacbb15948cf24c786ebbb92213a2fe013 Heikki Linnakangas pushed: - Fix outdated comment. Multi-insert records observe XLOG_HEAP_INIT_PAGE flag too, as Andres Freund pointed out. http://git.postgresql.org/pg/commitdiff/60a3dffb724c49c60d9ba921929bfa49ec21dd00 - Copy-editing 9.2 release notes. Fix a couple of typos, add missing filename tags, and add a link to the doc section on timezone guc. http://git.postgresql.org/pg/commitdiff/3e8e692bbc829f48c8c1accbeed9284735f9a88c - Fix a couple of typos in 9.2 release notes. Thom Brown http://git.postgresql.org/pg/commitdiff/386bb92f6348bf8a6f5ebd39122161e190e464c2 - On GiST page split, release the locks on child pages before recursing up. When inserting the downlinks for a split gist page, we used hold the locks on the child pages until the insertion into the parent - and recursively its parent if it had to be split too - were all completed. Change that so that the locks on child pages are released after the insertion in the immediate parent is done, before recursing further up the tree. This reduces the number of lwlocks that are held simultaneously. Holding many locks is bad for concurrency, and in extreme cases you can even hit the limit of 100 simultaneously held lwlocks in a backend. If you're really unlucky, you can hit the limit while in a critical section, which brings down the whole system. This fixes bug #6629 reported by Tom Forbes. Backpatch to 9.1. The page splitting code was rewritten in 9.1, and the old code did not have this problem. http://git.postgresql.org/pg/commitdiff/3652d72dd45b3ef2ca5e83e8cbd09f78696ad4c4 Robert Haas pushed: - Prevent loss of init fork when truncating an unlogged table. Fixes bug #6635, reported by Akira Kurosawa. http://git.postgresql.org/pg/commitdiff/1331cc6c1ad2beba7985523508d6722dc865c337 == Rejected Patches (for now) == No one was disappointed this week :-) == Pending Patches == Robert Haas sent in several approaches to optimizing CLOG background writing. Zoltan Boszormenyi sent in two more revisions of the patch to create and use a locktimeout and SIGALARM framework. Pavel Stehule sent in another revision of the patch to add an enhanced ErrorData structure to PL/pgsql. Magnus Hagander sent in a patch to fix a bug where pg_receivelog didn't handle timeouts correctly. Antonin Houska sent in a patch to implement some more of the LATERAL functionality via functions. Jeff Janes sent in a patch against pgbench which adds a --foreign-keys option to initialization mode which creates all the relevant constraints between the default tables. Noah Misch sent in a patch which updates code comments per PGPROC/PGXACT split. ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> David Fetter 2012-05-14T05:52:44 Postgres-XC 1.0beta2 is released http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2034 <pre>Hi all, Postgres-XC, write-scalable multi-master symmetric cluster based on PostgreSQL, version 1.0beta2 has been released. This beta version is based on PostgreSQL 9.1.3. All the patches in PostgreSQL 9.1 stable branch have been merged up to commit 1c0e678 (4th of May 2012). You can download the tarball directly from here: https://sourceforge.net/projects/postgres-xc/files/latest/download This tarball contains all the HTML and man documentation. The following enhancements have been made since release of 1.0beta1: - Redaction of release notes, summarizing all the features added in Postgres-XC since the creation of the project - Support for make world - Regressions stabilized (no failures for 139 tests) - Fix of more than 50 bugs. - Merge with stable branch of PostgreSQL 9.1 (600~ commits). Compared to version Postgres-XC 0.9.7, the following features have been added: - Fast query shipping (FQS), quick identification of expressions in a query that can be pushed down to remote nodes - SERIAL types - TABLESPACE - Utility to clean up 2PC transactions in cluster (pgxc_clean) - Utility for initialization of GTM (global transaction manager, utility called initgtm) - Relation-size functions - Regression stabilization The release notes of 1.0 are directly available here: http://postgres-xc.sourceforge.net/docs/1_0/release-xc-1-0.html. The project can be followed on Source Forge: http://postgres-xc.sourceforge.net/. And the project uses a couple of GIT repositories for development: - SourceForge: http://postgres-xc.git.sourceforge.net/git/gitweb.cgi?p=postgres-xc/postgres-xc;a=summary - Github: https://github.com/postgres-xc/postgres-xc Postgres-XC 1.0beta2 will be used during the Postgres-XC tutorial at PGCon in Ottawa, so be sure to touch this beta version to have an idea of what Postgres-XC is before attending! Thanks, </pre> Michael Paquier 2012-05-13T03:59:11 AnySQL Maestro 12.5 released http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2033 <pre>Hi! SQL Maestro Group announces the release of AnySQL Maestro 12.5, a powerful tool for managing any database engine accessible via ODBC driver or OLE DB provider (PostgreSQL, MySQL, SQL Server, Oracle, Access, etc). The new version is immediately available at http://www.sqlmaestro.com/products/anysql/maestro/ AnySQL Maestro comes in both Freeware and Professional editions. The feature matrix can be found at http://www.sqlmaestro.com/products/anysql/maestro/free_vs_pro/ Top 10 new features: =================== 1. Report Designer. 2. Support for auto increment columns for MS SQL Server and MS Access. 3. SQL Editors: Unicode support, text change markers, and improved code folding appearance. 4. Enhanced performance of the SQL Script Editor tool. 5. Improved Script Runner. 6. Inline images in the data grid. 7. Displaying BLOB data as PDF. 8. Creation of views from Visual Query Builder. 9. Updated Data Input form. 10. Spanish translation. In addition to this, several bugs have been fixed and some other minor improvements and corrections have been made. Full press-release (with explaining screenshots) is available at: http://www.sqlmaestro.com/news/company/anysql_maestro_12_5_released/ Background information: ================ SQL Maestro Group offers complete database admin and management tools for MySQL, Oracle, MS SQL Server, DB2, PostgreSQL, SQL Anywhere, SQLite, Firebird and MaxDB providing the highest performance, scalability and reliability to meet the requirements of today's database applications. Sincerely yours, The SQL Maestro Group Team http://www.sqlmaestro.com ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> SQL Maestro Group 2012-05-10T12:46:55 PostgreSQL Session #4 : Call for Papers http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2032 <pre>====== PostgreSQL Session #4 : Call for Papers ====== After three successful sessions dedicated to the new features of PostgreSQL 9.0 (february 2011), to PostGIS (june 2011), and to replication systems (february 2012), we'd like to announce that the 4th PostgreSQL Session will be held on October 4th, 2012, in Paris, France. More informations at: http://www.postgresql-sessions.org/en/4/ The topic of the conference will be: "Migrate to PostgreSQL" We're launching a call for paper for this event. You can now submit your talks, in English or in French. Each talk should last 45 minutes (questions included) and should focus on the topic of the event. We are interested in any talk about the following subjects: * Database migration (ora2pg, ETL, etc.) * Application migration * Partitioning in PostgreSQL * Managing a cluster of PostgreSQL servers * Replication and High-Availability * Foreign Data Wrappers (oracle_fdw, mysql_fdw, tds_fdw) * TCO Comparison of DMBS Talks can be either: a case study, a Proof of Concept, a tutorial, a benchmark, a presentation of a new feature, etc. Of course, we're open to propositions on any other mogration related topics (monitoring, hardware replication, etc.) ! The submission deadline is June 30th, 2012. Selected speakers will be notified before July 15th, 2012. You can now send your proposals to call-for-paper&lt; at &gt;postgresql-sessions.org Please give us a little information about you and your talk, such as: * First Name and Last Name * Twitter Account (if any) * Company * Short Biography (contributions to the PostgreSQL community) * Talk title * Talk abstract * Any specific need Slides should be in a free licence (Creative Commons BY-ND 3.0 or compatible), and will be available to Dalibo. See you in Paris next October ! **About the postgreSQL Sessions** : The PostgreSQL sessions are designed to be a time to discover and meet the PostgreSQL community. Each session is a day consisting of lectures and workshops, organized around a specific theme and a guest. The proposed talks aimed at all levels and all profiles: Developer, Administrator, Project Managers, IT Managers, ... The **PostgreSQL sessions** are organized by Dalibo, the french leading PostgreSQL company. Entry is free and open to all, within the limits of available seats. **About Dalibo** : Since 2005, Dalibo is the leading French PostgreSQL company and provides its experience and expertise to its clients in Europe. The company delivers a full range of PostgreSQL services : Trainings, Development, Performance Tuning, High Availibilty Setup, Migration Oracle to PostgreSQL, Troubleshooting and PostgreSQL support. Dalibo reserves the right to change the date and location of the event if the situation requires it. </pre> Guillaume Lelarge 2012-05-09T16:09:41 PL/Proxy 2.4 http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2031 <pre>New version of PL/Proxy is out. Main change is that default remote username is now taken from current_user, not session_user. Also internal connection cache now supports having connections to same cluster under different usernames. Both changes together make SECURITY DEFINER functions work sensibly. Old behaviour was targeted to support obscure security schemes for connect strings, but this is now obsoleted by SQL/MED. More details: http://pgfoundry.org/frs/shownotes.php?release_id=1947 Downloads: http://pgfoundry.org/projects/plproxy/ About PL/Proxy -------------- PL/Proxy is database partitioning system implemented as PL language. Homepage: http://wiki.postgresql.org/wiki/PL/Proxy GIT: http://git.postgresql.org/gitweb?p=plproxy.git;a=summary Github: https://github.com/markokr/plproxy-dev List: http://lists.pgfoundry.org/mailman/listinfo/plproxy-users ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> Marko Kreen 2012-05-07T19:07:38 Announcing pgXplorer - a new GUI for postgres http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2030 <pre>Greetings everyone. I have just released pgXplorer - a new GUI for postgres 8.4+. You can download the installers for Mac, Windows and Ubuntu from pgxplorer.com. The code is open sourced under the ISC license and can be found on github at: https://github.com/davyjones/pgXplorer Please raise any issues or concerns at the projects' github page. Thanks, dj ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> dj< at >pgxplorer.com 2012-05-06T08:54:23 == PostgreSQL Weekly News - May 06 2012 == http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2029 <pre>== PostgreSQL Weekly News - May 06 2012 == PostgreSQL conference China 2012 will be on June 14-17, 2012 in Beijing. http://wiki.postgresql.org/wiki/Pgconfchina2012 PostgreSQL Magazine #01 is out now. http://pgmag.org/01/ PostgreSQL Turkey User Group is organizing 2nd Turkish PostgreSQL Conference in Istanbul, on May 12, 2012. Magnus Hagander will be giving the keynote. Please register for free: http://pgday.PostgreSQL.org.tr/2012/ == PostgreSQL Product News == ODB 2.0.0, an ORM for C++, supports PostgreSQL. http://www.codesynthesis.com/pipermail/odb-announcements/2012/000013.html == PostgreSQL Jobs for May == http://archives.postgresql.org/pgsql-jobs/2012-05/threads.php == PostgreSQL Local == PGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of Ottawa. It will be preceded by two days of tutorials on 15-16 May 2012. http://www.pgcon.org/2012/ PGDay France will be in Lyon on June 7, 2012. http://www.pgday.fr PostgreSQL Conference Europe 2012 will be in Prague, Czech Republic on October 23-26. The call for sponsors is open. http://2012.pgconf.eu/ == PostgreSQL in the News == Planet PostgreSQL: http://planet.postgresql.org/ PostgreSQL Weekly News is brought to you this week by David Fetter Submit news and announcements by Sunday at 3:00pm Pacific time. Please send English language ones to david&lt; at &gt;fetter.org, German language to pwn&lt; at &gt;pgug.de, Italian language to pwn&lt; at &gt;itpug.org. Spanish language to pwn&lt; at &gt;arpug.com.ar. == Reviews == == Applied Patches == Bruce Momjian pushed: - Add comments suggesting usage of git_changelog to generate release notes. http://git.postgresql.org/pg/commitdiff/f33fe47a9169eec692b80c17ea47bd2f9c261aaf - Mark git_changelog examples with the proper executable names. http://git.postgresql.org/pg/commitdiff/7490c48f1e2c51dce77d33f7fd464e72713679a5 - Remove BSD/OS (BSDi) port. There are no known users upgrading to Postgres 9.2, and perhaps no existing users either. http://git.postgresql.org/pg/commitdiff/ebcaa5fcde8411786e3765414465174e6d31c8e6 - Fix psql doc typo. http://git.postgresql.org/pg/commitdiff/768c3affd44d1dcb4e43e2e006c642524714c2a4 - Revert typo fix 768c3affd44d1dcb4e43e2e006c642524714c2a4; I was wrong. http://git.postgresql.org/pg/commitdiff/0a3a674b98ebb47e2f4b539a0e284744a7871987 - Document that it is the pgsql version we are matching for psqlrc version-specific files, not the server version. http://git.postgresql.org/pg/commitdiff/65b110703b798cdbfa568aa3583caba0ed51b33a Robert Haas pushed: - Remove duplicate word in comment. Noted by Peter Geoghegan. http://git.postgresql.org/pg/commitdiff/0d2235a25bc71848c18f551f992b3eed8cec2399 - Tweak psql to print row counts when \x auto chooses non-expanded output. Noah Misch http://git.postgresql.org/pg/commitdiff/9b7a84f2a45322b21b86eb180a869d1ed2937b85 - More duplicate word removal. http://git.postgresql.org/pg/commitdiff/e01e66f808fbd161b2714eab34bb9e9d0db0db53 - Further corrections from the department of redundancy department. Thom Brown http://git.postgresql.org/pg/commitdiff/1b4998fd44bad9f8ab90e741cadd6519f6c94a44 - Avoid repeated CLOG access from heap_hot_search_buffer. At the time we check whether the tuple is dead to all running transactions, we've already verified that it isn't visible to our scan, setting hint bits if appropriate. So there's no need to recheck CLOG for the all-dead test we do just a moment later. So, add HeapTupleIsSurelyDead() to test the appropriate condition under the assumption that all relevant hit bits are already set. Review by Tom Lane. http://git.postgresql.org/pg/commitdiff/003811042139790a5a479c8264271a3248eda36f - Add missing parenthesis in comment. http://git.postgresql.org/pg/commitdiff/8e0c5195dff70ffc9c132716d0cf7f3eff45e302 Peter Eisentraut pushed: - Mark ReThrowError() with attribute noreturn. All related functions were already so marked. http://git.postgresql.org/pg/commitdiff/26471a51fc833e2ce58a2f16f891256d57dd28c6 - Improve markup of cmdsynopsis elements. Add more markup in particular so that the command options appear consistently in monospace in the HTML output. On the vacuumdb reference page, remove listing all the possible options in the synopsis. They have become too many now; we have the detailed options list for that. http://git.postgresql.org/pg/commitdiff/4266509c577b089627930af39f1dcd2d06b493e9 - Fix display of &lt;command&gt; elements on man pages. We had changed this from the default bold to monospace for all output formats, but for man pages, this creates visual inconsistencies, so revert to the default for man pages. http://git.postgresql.org/pg/commitdiff/61c84b47619c11e74089cb3160813a4b3c98e6d7 - Remove dead ports. Remove the following ports: dgux, nextstep, sunos4, svr4, ultrix4, and univel. These are obsolete and not worth rescuing. In most cases, there is circumstantial evidence that they wouldn't work anymore anyway. http://git.postgresql.org/pg/commitdiff/f2f9439fbfba378cb64cd6e5a046e0184cd542c6 - Even more duplicate word removal, in the spirit of the season http://git.postgresql.org/pg/commitdiff/e9605a039b60350003daf8a5b3c0c10993994b60 - PL/Python: Fix crash in functions returning SETOF and using SPI. Allocate PLyResultObject.tupdesc in TopMemoryContext, because its lifetime is the lifetime of the Python object and it shouldn't be freed by some other memory context, such as one controlled by SPI. We trust that the Python object will clean up its own memory. Before, this would crash the included regression test case by trying to use memory that was already freed. reported by Asif Naeem, analysis by Tom Lane http://git.postgresql.org/pg/commitdiff/52aa334fcd5a9d230be7e8fb964d94c6c4e63dc7 - doc: Fix for too many brackets in command synopses on man pages. The default for the choice attribute of the &lt;arg&gt; element is "opt", which would normally put the argument inside brackets. But the DSSSL stylesheets contain a hack that treats &lt;arg&gt; directly inside &lt;group&gt; specially, so that &lt;group&gt;&lt;arg&gt;-x&lt;/arg&gt;&lt;arg&gt;-y&lt;/arg&gt;&lt;/group&gt; comes out as [ -x | -y ] rather than [ [-x] | [-y] ], which it would technically be. But when building man pages, this doesn't work, and so the command synopses on the man pages contain lots of extra brackets. By putting choice="opt" or choice="plain" explicitly on every &lt;arg&gt; and &lt;group&gt; element, we avoid any toolchain dependencies like that, and it also makes it clearer in the source code what is meant. In passing, make some small corrections in the documentation about which arguments are really optional or not. http://git.postgresql.org/pg/commitdiff/1715ff112809bca5218ddb6eccfda2c20dc420b5 - PL/Python: Improve test coverage. Add test cases for inline handler of plython2u (when using that language name), and for result object element assignment. There is now at least one test case for every top-level functionality, except plpy.Fatal (annoying to use in regression tests) and result object slice retrieval and slice assignment (which are somewhat broken). http://git.postgresql.org/pg/commitdiff/e6c2e8cb87846161033e1f215876c4b95f631df0 Tom Lane pushed: - Converge all SQL-level statistics timing values to float8 milliseconds. This patch adjusts the core statistics views to match the decision already taken for pg_stat_statements, that values representing elapsed time should be represented as float8 and measured in milliseconds. By using float8, we are no longer tied to a specific maximum precision of timing data. (Internally, it's still microseconds, but we could now change that without needing changes at the SQL level.) The columns affected are pg_stat_bgwriter.checkpoint_write_time, pg_stat_bgwriter.checkpoint_sync_time, pg_stat_database.blk_read_time, pg_stat_database.blk_write_time, pg_stat_user_functions.total_time, pg_stat_user_functions.self_time, pg_stat_xact_user_functions.total_time, and pg_stat_xact_user_functions.self_time. The first four of these are new in 9.2, so there is no compatibility issue from changing them. The others require a release note comment that they are now double precision (and can show a fractional part) rather than bigint as before; also their underlying statistics functions now match the column definitions, instead of returning bigint microseconds. http://git.postgresql.org/pg/commitdiff/809e7e21af8cd24855f1802524a13bbaa823f929 - Kill some remaining references to SVR4 and univel. Both terms still appear in a few places, but I thought it best to leave those alone in context. http://git.postgresql.org/pg/commitdiff/50c2d6a1a63f04fd8c4553fc696c2c9e235b1a25 - Overdue code review for transaction-level advisory locks patch. Commit 62c7bd31c8878dd45c9b9b2429ab7a12103f3590 had assorted problems, most visibly that it broke PREPARE TRANSACTION in the presence of session-level advisory locks (which should be ignored by PREPARE), as per a recent complaint from Stephen Rees. More abstractly, the patch made the LockMethodData.transactional flag not merely useless but outright dangerous, because in point of fact that flag no longer tells you anything at all about whether a lock is held transactionally. This fix therefore removes that flag altogether. We now rely entirely on the convention already in use in lock.c that transactional lock holds must be owned by some ResourceOwner, while session holds are never so owned. Setting the locallock struct's owner link to NULL thus denotes a session hold, and there is no redundant marker for that. PREPARE TRANSACTION now works again when there are session-level advisory locks, and it is also able to transfer transactional advisory locks to the prepared transaction, but for implementation reasons it throws an error if we hold both types of lock on a single lockable object. Perhaps it will be worth improving that someday. Assorted other minor cleanup and documentation editing, as well. Back-patch to 9.1, except that in the 9.1 branch I did not remove the LockMethodData.transactional flag for fear of causing an ABI break for any external code that might be examining those structs. http://git.postgresql.org/pg/commitdiff/71b9549d053b2f0a9e76e829c917385841f84bee Heikki Linnakangas pushed: - Remove duplicate words in comments. Found these with grep -r "for for ". http://git.postgresql.org/pg/commitdiff/f291ccd43e06fdd7c55102975a0b2f38bc140b90 Magnus Hagander pushed: - Remove link to ODBCng project from the docs. This backatches Heikki's patch in 140a4fbf1a87891a79a2c61a08416828d39f286a to make sure the documentation on the website gets updated, since we're regularly receiving complains about this link. http://git.postgresql.org/pg/commitdiff/6d362ec209f0174f36a78936c5269f8d5f2cd26e == Rejected Patches (for now) == No one was disappointed this week :-) == Pending Patches == Ryan Kelly sent in another revision of the patch to allow breaking out of hung connection attempts in libpq. Noah Misch sent in a patch to prevent a theoretical torn page hazard in ginRedoUpdateMetapage(). Pavel Stehule sent in a patch to add new error fields to PL/pgsql. Laurenz Albe sent in another revision of the patch to analyze foreign tables which gets the FDW to show that a value was non-NULL but removed due to excess width by returning a value of length WIDTH_THRESHOLD+1. Peter Geoghegan sent in two revisions of a patch to latch up the WAL Writer, reducing wake-ups and thus saving electricity in a way that is more-or-less analogous to his previous work on the BGWriter. Magnus Hagander sent in a patch to reduce the number of "Unexpected EOF on client connection" messages clogging people's logs. Jan Urbanski sent in a patch to fix an issue with PL/PythonU where result set slicing was broken in the Python3 case. ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> David Fetter 2012-05-07T03:54:59 PostgreSQL conference China 2012 Announced! http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2028 <pre>PostgreSQL conference China 2011 will be hold in June 14-17 in Beijing, China. PostgresQL User Group Conference China which organized by CPUG(China Postgres User Group) is an annual conference for PostgreSQL users in China, the conference is a hub for learning new features, sharing the know-how, and making friends about PostgreSQL. PostgresQL User Group Conference China 2012 will be on 14-17 June 2012 at Renmin University of China in Beijing with two days of Tutorials on 14-15 June 2012. Magnus Hagander,Simon Rigg and Suzuki Koichi from community will also join this conference to give keynote speeches. A Two-day free Postgres DBA training will be given for people who want to learn PostgreSQL administration in the first two days. In 16-17 June, and the conference will be organized in three tracks, PostgreSQL experts from local and community will give talks about: - System architecture for using PostgreSQL - Migration of production systems from another database - Data warehousing - Tuning PostgreSQL for different work loads - Replication and clustering - Benchmarking and performance engineering - Case studies - Location-aware and mapping software with PostGIS - PostgreSQL 9.2 features - Kernel devolopment - Research and teaching with PostgreSQL Community major developers: Simmon Rigg, Suzuki Koichi will give talks about 9.2 features, PG-XC and clustering solutions. Please join us in this conference! This conference is organized by Galy Lee(galylee((at)gmail(dot)com), if you have any question, please contact him . For detail please refer to the conference page: http://wiki.postgresql.org/wiki/Pgconfchina2012 Best Regards Galy </pre> galy lee 2012-05-06T11:12:30 ODB C++ ORM 2.0.0 released, adds support for C++11, polymorphism http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2027 <pre>I am pleased to announce the release of ODB 2.0.0. ODB is an open source object-relational mapping (ORM) system for C++. It allows you to persist C++ objects to a relational database without having to deal with tables, columns, or SQL and without manually writing any of the mapping code. Major new features in this release: * Support for C++11 which adds integration with the new C++11 standard library components, including smart pointers and containers. Now you can use std::unique_ptr and std::shared_ptr as object pointers (their lazy versions are also provided). For containers, support was added for std::array, std::forward_list, and the unordered containers. * Support for polymorphism which allows you to persist, load, update, erase, and query objects of derived classes using their base class interfaces. Persistent class hierarchies are mapped to the relational database model using the table-per-difference mapping. * Support for composite object ids which are translated to composite primary keys in the relational database. * Support for the NULL semantics for composite values. This release has also been tested with GCC 4.7 and Clang 3.0 with the ODB compiler now supporting the GCC 4.7 series plugin interface. With this release we are also introducing a free proprietary license for small object models. A more detailed discussion of these features can be found in the following blog post: http://www.codesynthesis.com/~boris/blog/2012/05/02/odb-2-0-0-released/ For the complete list of new features in this version see the official release announcement: http://www.codesynthesis.com/pipermail/odb-announcements/2012/000013.html ODB is written in portable C++ and you should be able to use it with any modern C++ compiler. In particular, we have tested this release on GNU/Linux (x86/x86-64), Windows (x86/x86-64), Mac OS X, and Solaris (x86/x86-64/SPARC) with GNU g++ 4.2.x-4.7.x, MS Visual C++ 2008 and 2010, Sun Studio 12, and Clang 3.0. The currently supported database systems are PostgreSQL, MySQL, SQLite, Oracle, and SQL Server. ODB also provides profiles for Boost and Qt, which allow you to seamlessly use value types, containers, and smart pointers from these libraries in your persistent classes. More information, documentation, source code, and pre-compiled binaries are available from: http://www.codesynthesis.com/products/odb/ Enjoy, Boris ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> Boris Kolpackov 2012-05-02T12:33:44 PostgreSQL Magazine #01 is out ! http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2026 <pre>I'm very pleased to announce the release of the first issue of PostgreSQL Magazine. This issue #01 is brought to you thanks to the collective work of dozen of people. Writers, Editors, Reviewers. Kudos to them all ! Here's a quick view of the ToC : - PostgreSQL 9.1 : 10 awesome new features - NoSQL : The Key Value store everyone ignored - Interview : Stefan Kaltenbrunner - Opinion : Funding PostgreSQL Features - Waiting for 9.2 : Cascading Streaming Replication - Tips &amp; Tricks : PostgreSQL in Mac OS X Lion The magazine is available online and on paper. You can either : * Read it Online: http://pgmag.org/01/read * Buy the Print Edition: http://pgmag.org/01/buy * or Download the PDF: http://pgmag.org/01/download Finally, I would like to thank our benefactors… Fotolia.com has offered us a free subscription plan to access their stock photo database. We also received fundings from PostgreSQL Europe (PGEU) and Software in the Public Interest (SPI). Thanks a lot to them ! </pre> PostgreSQL Magazine 2012-05-01T21:22:40 == PostgreSQL Weekly News - April 29 2012 == http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2025 <pre>== PostgreSQL Weekly News - April 29 2012 == == PostgreSQL Jobs for April == http://archives.postgresql.org/pgsql-jobs/2012-04/threads.php == PostgreSQL Local == PGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of Ottawa. It will be preceded by two days of tutorials on 15-16 May 2012. http://www.pgcon.org/2012/ PGDay France will be in Lyon on June 7, 2012. http://www.pgday.fr PostgreSQL Conference Europe 2012 will be in Prague, Czech Republic on October 23-26. The call for sponsors is open. http://2012.pgconf.eu/ == PostgreSQL in the News == Planet PostgreSQL: http://planet.postgresql.org/ PostgreSQL Weekly News is brought to you this week by David Fetter Submit news and announcements by Sunday at 3:00pm Pacific time. Please send English language ones to david&lt; at &gt;fetter.org, German language to pwn&lt; at &gt;pgug.de, Italian language to pwn&lt; at &gt;itpug.org. Spanish language to pwn&lt; at &gt;arpug.com.ar. == Reviews == == Applied Patches == Robert Haas pushed: - Minor improvements for CHECK NO INHERIT documentation. Fix typo spotted by Thom Brown, and improve wording in another area where Thom spotted a typo. http://git.postgresql.org/pg/commitdiff/9d435d57e1f8ec7e51d40722854252875d8cc6eb - Reduce hash size for compute_array_stats, compute_tsvector_stats. The size is only a hint, but a big hint chews up a lot of memory without apparently improving performance much. Analysis and patch by Noah Misch. http://git.postgresql.org/pg/commitdiff/85efd5f06593b80bbe01e541d78b336c1077213e - Rearrange lazy_scan_heap to avoid visibility map race conditions. We must set the visibility map bit before releasing our exclusive lock on the heap page; otherwise, someone might clear the heap page bit before we set the visibility map bit, leading to a situation where the visibility map thinks the page is all-visible but it's really not. This problem has existed since 8.4, but it wasn't critical before we had index-only scans, since the worst case scenario was that the page wouldn't get vacuumed until the next scan_all vacuum. Along the way, a couple of minor, related improvements: (1) if we pause the heap scan to do an index vac cycle, release any visibility map page we're holding, since really long-running pins are not good for a variety of reasons; and (2) warn if we see a page that's marked all-visible in the visibility map but not on the page level, since that should never happen any more (it was allowed in previous releases, but not in 9.2). http://git.postgresql.org/pg/commitdiff/7ab9b2f3b79177e501a1ef90ed004cc68788abaf - Lots of doc corrections. Josh Kupershmidt http://git.postgresql.org/pg/commitdiff/5d4b60f2f25bedee257aaf6f2f4ac77028629b87 - Another typographical correction. Noted by Guillaume Smet. http://git.postgresql.org/pg/commitdiff/e4f06b70c9ac1473591d705990a8b601915ce4bd - Casts to or from a domain type are ignored; warn and document. Prohibiting this outright would break dumps taken from older versions that contain such casts, which would create far more pain than is justified here. Per report by Jaime Casanova and subsequent discussion. http://git.postgresql.org/pg/commitdiff/3ce7f18e92e9687308ed5d9e516eb7e2f0decadb - Remove prototype for nonexistent function. http://git.postgresql.org/pg/commitdiff/ca1e1a8da11d188df738ba67632c0805a00d3f27 - Prevent index-only scans from returning wrong answers under Hot Standby. The alternative of disallowing index-only scans in HS operation was discussed, but the consensus was that it was better to treat marking a page all-visible as a recovery conflict for snapshots that could still fail to see XIDs on that page. We may in the future try to soften this, so that we simply force index scans to do heap fetches in cases where this may be an issue, rather than throwing a hard conflict. http://git.postgresql.org/pg/commitdiff/3424bff90f40532527b9cf4f2ad9eaff750682f7 Peter Eisentraut pushed: - Fix minor stylistic issue http://git.postgresql.org/pg/commitdiff/225d9c063820237c979c918cf735bf98cbd566c0 - entab: Improve makefile. A few simplifications and stylistic improvements, found while grepping around for makefile problems elsewhere. http://git.postgresql.org/pg/commitdiff/8bd44677df7f5139afa6d6a2d8f5a92e2db54cba - Standardize indentation of XSL files. Predominant standard is two spaces, so adjust outliers to that. http://git.postgresql.org/pg/commitdiff/2856c51c86857f2df674a37609515d26311062e9 - PL/Python: Improve error messages http://git.postgresql.org/pg/commitdiff/65ca8e68b7b21de7641d8ec9b7d4b9a2dd5e081d - psql: Tab completion updates. Add/complete support for: ALTER DOMAIN / VALIDATE CONSTRAINT, ALTER DOMAIN / RENAME, ALTER DOMAIN / RENAME CONSTRAINT, ALTER TABLE / RENAME CONSTRAINT, http://git.postgresql.org/pg/commitdiff/cc71ceab57d763f8f443346badd8e826b3b09e6e - PL/Python: Accept strings in functions returning composite types.. Before 9.1, PL/Python functions returning composite types could return a string and it would be parsed using record_in. The 9.1 changes made PL/Python only expect dictionaries, tuples, or objects supporting getattr as output of composite functions, resulting in a regression and a confusing error message, as the strings were interpreted as sequences and the code for transforming lists to database tuples was used. Fix this by treating strings separately as before, before checking for the other types. The reason why it's important to support string to database tuple conversion is that trigger functions on tables with composite columns get the composite row passed in as a string (from record_out). Without supporting converting this back using record_in, this makes it impossible to implement pass-through behavior for these columns, as PL/Python no longer accepts strings for composite values. A better solution would be to fix the code that transforms composite inputs into Python objects to produce dictionaries that would then be correctly interpreted by the Python-&gt;PostgreSQL counterpart code. But that would be too invasive to backpatch to 9.1, and it is too late in the 9.2 cycle to attempt it. It should be revisited in the future, though. Reported as bug #6559 by Kirill Simonov. Jan Urbański http://git.postgresql.org/pg/commitdiff/ba3e4157a7d0c7e963a8b800a30b9789aea6dd96 - PL/Python: Update list of supported environment variables http://git.postgresql.org/pg/commitdiff/05dd9fb18d6572f1467f995085b1de324d0ad028 - Change return type of ExceptionalCondition to void and mark it noreturn. In ancient times, it was thought that this wouldn't work because of TrapMacro/AssertMacro, but changing those to use a comma operator appears to work without compiler warnings. http://git.postgresql.org/pg/commitdiff/81107282a5ff1490a0a4ded193cbc61e69cda537 - Simplify makefile rule. Instead of writing out the .c -&gt; .o rule, use the default one, so that dependency tracking can be used. http://git.postgresql.org/pg/commitdiff/2227bb9c948d2dcc167d414630ed3bae7f31db83 Tom Lane pushed: - Another trivial comment-typo fix. http://git.postgresql.org/pg/commitdiff/9873001e6d1177d543a2e46273e738d726670f1f - Fix edge-case behavior of pg_next_dst_boundary(). Due to rather sloppy thinking (on my part, I'm afraid) about the appropriate behavior for boundary conditions, pg_next_dst_boundary() gave undefined, platform-dependent results when the input time is exactly the last recorded DST transition time for the specified time zone, as a result of fetching values one past the end of its data arrays. Change its specification to be that it always finds the next DST boundary *after* the input time, and adjust code to match that. The sole existing caller, DetermineTimeZoneOffset, doesn't actually care about this distinction, since it always uses a probe time earlier than the instant that it does care about. So it seemed best to me to change the API to make the result=1 and result=0 cases more consistent, specifically to ensure that the "before" outputs always describe the state at the given time, rather than hacking the code to obey the previous API comment exactly. Per bug #6605 from Sergey Burladyan. Back-patch to all supported versions. http://git.postgresql.org/pg/commitdiff/c62b8eaae11aaa69a2b71bc63f9f78ca72eb412c - Fix planner's handling of RETURNING lists in writable CTEs. setrefs.c failed to do "rtoffset" adjustment of Vars in RETURNING lists, which meant they were left with the wrong varnos when the RETURNING list was in a subquery. That was never possible before writable CTEs, of course, but now it's broken. The executor fails to notice any problem because ExecEvalVar just references the ecxt_scantuple for any normal varno; but EXPLAIN breaks when the varno is wrong, as illustrated in a recent complaint from Bartosz Dmytrak. Since the eventual rtoffset of the subquery is not known at the time we are preparing its plan node, the previous scheme of executing set_returning_clause_references() at that time cannot handle this adjustment. Fortunately, it turns out that we don't really need to do it that way, because all the needed information is available during normal setrefs.c execution; we just have to dig it out of the ModifyTable node. So, do that, and get rid of the kluge of early setrefs processing of RETURNING lists. (This is a little bit of a cheat in the case of inherited UPDATE/DELETE, because we are not passing a "root" struct that corresponds exactly to what the subplan was built with. But that doesn't matter, and anyway this is less ugly than early setrefs processing was.) Back-patch to 9.1, where the problem became possible to hit. http://git.postgresql.org/pg/commitdiff/9fa82c980935ef4aee18fabe8da20ae2198b052a - Modify create_index regression test to avoid intermittent failures. We have been seeing intermittent buildfarm failures due to a query sometimes not using an index-only scan plan, because a background auto-ANALYZE prevented the table's all-visible bits from being set immediately, thereby causing the estimated cost of an index-only scan to go up considerably. Adjust the test case so that a bitmap index scan is preferred instead, which serves equally well for the purpose the test case is actually meant for. (Of course, it would be better to eliminate the interference from auto-ANALYZE, but I see no low-risk way to do that, so any such fix will have to be left for 9.3 or later.) http://git.postgresql.org/pg/commitdiff/d6d5f67b5b98b1685f9158e9d00a726afb2ae789 - Fix oversight in recent parameterized-path patch. bitmap_scan_cost_est() has to be able to cope with a BitmapOrPath, but I'd taken a shortcut that didn't work for that case. Noted by Heikki. Add some regression tests since this area is evidently under-covered. http://git.postgresql.org/pg/commitdiff/7c85aa39fc08df44e1ce67e651bda4cf7e331580 - Improve documentation around historical calendar rules. Get rid of section 8.5.6 (Date/Time Internals), which appears to confuse people more than it helps, and anyway discussion of Postgres' internal datetime calculation methods seems pretty out of place here. Instead, make datatype.sgml just say that we follow the Gregorian calendar (a bit of specification not previously present anywhere in that chapter :-() and link to the History of Units appendix for more info. Do some mild editorialization on that appendix, too, to make it clearer that we are following proleptic Gregorian calendar rules rather than anything more historically accurate. Per a question from Florence Cousin and subsequent discussion in pgsql-docs. http://git.postgresql.org/pg/commitdiff/92df2203437603d40417fe711c3cb7066ac4fdf5 - Fix syslogger's rotation disable/re-enable logic. If it fails to open a new log file, the syslogger assumes there's something wrong with its parameters (such as log_directory), and stops attempting automatic time-based or size-based log file rotations. Sending it SIGHUP is supposed to start that up again. However, the original coding for that was really bogus, involving clobbering a couple of GUC variables and hoping that SIGHUP processing would restore them. Get rid of that technique in favor of maintaining a separate flag showing we've turned rotation off. Per report from Mark Kirkwood. Also, the syslogger will automatically attempt to create the log_directory directory if it doesn't exist, but that was only happening at startup. For consistency and ease of use, it should do the same whenever the value of log_directory is changed by SIGHUP. Back-patch to all supported branches. http://git.postgresql.org/pg/commitdiff/537b26695389ae67adc4fbbe04254bc527a11128 - Fix printing of whole-row Vars at top level of a SELECT targetlist. Normally whole-row Vars are printed as "tabname.*". However, that does not work at top level of a targetlist, because per SQL standard the parser will think that the "*" should result in column-by-column expansion; which is not at all what a whole-row Var implies. We used to just print the table name in such cases, which works most of the time; but it fails if the table name matches a column name available anywhere in the FROM clause. This could lead for instance to a view being interpreted differently after dump and reload. Adding parentheses doesn't fix it, but there is a reasonably simple kluge we can use instead: attach a no-op cast, so that the "*" isn't syntactically at top level anymore. This makes the printing of such whole-row Vars a lot more consistent with other Vars, and may indeed fix more cases than just the reported one; I'm suspicious that cases involving schema qualification probably didn't work properly before, either. Per bug report and fix proposal from Abbas Butt, though this patch is quite different in detail from his. Back-patch to all supported versions. http://git.postgresql.org/pg/commitdiff/d6f7d4fdc516b2b597f8c2cd011c41c2729dab45 - Clear I/O timing counters after sending them to the stats collector. This oversight caused the reported times to accumulate in an O(N^2) fashion the longer a backend runs. http://git.postgresql.org/pg/commitdiff/cdbad241f41362aaf09f913722a541e04e048742 - Adjust timing units in pg_stat_statements. Display total time and I/O timings in milliseconds, for consistency with the units used for timings in the core statistics views. The columns remain of float8 type, so that sub-msec precision is available. (At some point we will probably want to convert the core views to use float8 type for the same reason, but this patch does not touch that issue.) This is a release-note-requiring change in the meaning of the total_time column. The I/O timing columns are new as of 9.2, so there is no compatibility impact from redefining them. Do some minor copy-editing in the documentation, too. http://git.postgresql.org/pg/commitdiff/93f94e356d47ea20ca7c2fcb65cbb746049fe4d1 - Make a copy-editing pass over the new documentation for statistics views. Fix a bunch of typos, improve markup, make wording more uniform, rearrange some material. No substantive changes. http://git.postgresql.org/pg/commitdiff/aebe989477ac5a9f7b59ae464ec68ec45975ed3f - Further editorialization on the new documentation for statistics views. Get rid of the per-column documentation of underlying functions, which did far more to clutter the view descriptions than it did to be helpful, and was rather incomplete and typo-ridden anyway. Instead suggest that people consult the definitions of the standard views to see the underlying functions. The older functions for obtaining individual facts about backends are now somewhat obsoleted by pg_stat_get_activity, which means that they are not documented by any standard view. So I put that information into a separate table. (Maybe we should just deprecate them instead?) In passing, fix a couple more documentation errors. http://git.postgresql.org/pg/commitdiff/5f2b0893871cce1ffb77ac7f13b3fba227e6f11f - Rename track_iotiming GUC to track_io_timing. This spelling seems significantly more readable to me. http://git.postgresql.org/pg/commitdiff/309c64745ea145d7c731e1fe610631b2b84e7e88 - Rename I/O timing statistics columns to blk_read_time and blk_write_time. This seems more consistent with the pre-existing choices for names of other statistics columns. Rename assorted internal identifiers to match. http://git.postgresql.org/pg/commitdiff/1dd89eadcd2648d7ca0baed3c7af16a04eb1aa26 Bruce Momjian pushed: - Add options to git_changelog for use in major release note creation: --details-after --master-only --oldest-first http://git.postgresql.org/pg/commitdiff/993ce4e6c9f23d385d60f1fd4aee01bdf050de24 == Rejected Patches (for now) == No one was disappointed this week :-) == Pending Patches == Zoltan Boszormenyi sent in another version of the patches to create a lock timeout framework and use same. Alexander Korotkov sent in a patch to convert from pg_wchar to multibyte, and Erik Rijkers followed up with some regression tests for same. KaiGai Kohei sent in another revision of the patch to add generic extra daemons. Noah Misch sent in a patch to fix an issue where psql does not include a row count when auto-expanded output (\x auto) is set. Kevin Grittner sent in a patch to fix an issue where setting defautl_transaction_isolation to serializable (SSI) broke Hot Standbys. Robert Haas sent in a patch to modify "smart" shutdown mode to disconnect sessions that are not in a transaction (or as soon as they no longer are) but leaves in-progress transactions alone; Noah Misch sent in a patch to allow TEMP tables on a hot standby. ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> David Fetter 2012-04-30T05:42:00 == PostgreSQL Weekly News - April 22 2012 == http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2024 <pre>== PostgreSQL Weekly News - April 22 2012 == PostgreSQL Conference Europe 2012 will be in Prague, Czech Republic on October 23-26. The call for sponsors is open. http://2012.pgconf.eu/ PGNext has been cancelled. == PostgreSQL Product News == pgbouncer 1.5.1, a light-weight connection pooler for PostgreSQL, released. http://pgfoundry.org/frs/shownotes.php?release_id=1936 pgpool-II 3.1.3 and 3.0.7, a multi-purpose middleware which can provide connection pooling, replication, load balancing, parallel execution and more, released. http://www.pgpool.net/download.php?f=pgpool-II-3.1.3.tar.gz http://www.pgpool.net/download.php?f=pgpool-II-3.0.7.tar.gz Skytools 3.0.1, a package of tools developed by Skype for replication and failover including PgQ, a generic queuing framework and Londiste, a row-based master-slave replication replication system, released: http://pgfoundry.org/projects/skytools == PostgreSQL Jobs for April == http://archives.postgresql.org/pgsql-jobs/2012-04/threads.php == PostgreSQL Local == The second meeting of Arizona PostgreSQL Users Group at 6:30 PM on Wednesday, April 25, and will start with pizza and refreshments. You can join the mailing list, and RSVP at: https://www.bigtent.com/groups/azpug PGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of Ottawa. It will be preceded by two days of tutorials on 15-16 May 2012. http://www.pgcon.org/2012/ PGDay France will be in Lyon on June 7, 2012. http://www.pgday.fr == PostgreSQL in the News == Planet PostgreSQL: http://planet.postgresql.org/ PostgreSQL Weekly News is brought to you this week by David Fetter Submit news and announcements by Sunday at 3:00pm Pacific time. Please send English language ones to david&lt; at &gt;fetter.org, German language to pwn&lt; at &gt;pgug.de, Italian language to pwn&lt; at &gt;itpug.org. Spanish language to pwn&lt; at &gt;arpug.com.ar. == Reviews == == Applied Patches == Peter Eisentraut pushed: - PL/Python: Improve documentation of nrows() method. Clarify that nrows() is the number of rows processed, versus the number of rows returned, which can be obtained using len. Also add tests about that. http://git.postgresql.org/pg/commitdiff/0f48e0675134eccd905eaf696a03c1e8cc85eab4 - Fix typo. Kyotaro HORIGUCHI http://git.postgresql.org/pg/commitdiff/a33fcd7e79d7e1544030160de177aee847bb7648 - Add compatibility information for prepared transaction commands http://git.postgresql.org/pg/commitdiff/cf714c81086a85b7558a84ebd024f6a5eec2a5ee - psql: Add tab completion for CREATE/ALTER ROLE name WITH. Previously, the use of the optional key word WITH was not supported. Josh Kupershmidt http://git.postgresql.org/pg/commitdiff/1fd832ddffe83a07f82939bd9e5787a61aeba1ef - Untabify DSSSL and XSL files and add to check-tabs target. Like with SGML files, using tabs in these files is confusing and unnecessary. http://git.postgresql.org/pg/commitdiff/cd1f4db4aec0c4b71d2ed0d29bbe388dfcd11527 - Fix some typos. Josh Kupershmidt http://git.postgresql.org/pg/commitdiff/48658a1b818060fcfb3c91704943c5fbcf10088e Heikki Linnakangas pushed: - Install plpgsql.h to to include/server at "make install". The header file is needed by any module that wants to use the PL/pgSQL instrumentation plugin interface. Most notably, the pldebugger plugin needs this. With this patch, it can be built using pgxs, without having the full server source tree available. http://git.postgresql.org/pg/commitdiff/49440fff08590cf1a764ab4b4c5342cd9e445991 - Don't wait for the commit record to be replicated if we wrote no WAL. When using synchronous replication, we waited for the commit record to be replicated, but if we our transaction didn't write any other WAL records, that's not required because we don't even flush the WAL locally to disk in that case. This lead to long waits when committing a transaction that only modified a temporary table. Bug spotted by Thom Brown. http://git.postgresql.org/pg/commitdiff/fe546f3da6a5ff1d879f587728f74ec457f0ee5f Andrew Dunstan pushed: - Don't override arguments set via options with positional arguments. A number of utility programs were rather careless about paremeters that can be set via both an option argument and a positional argument. This leads to results which can violate the Principal Of Least Astonishment. These changes refuse to use positional arguments to override settings that have been made via positional arguments. The changes are backpatched to all live branches. http://git.postgresql.org/pg/commitdiff/1b37a8c3cc4f0615f80d6007e2bbd47c6bd7e1e3 Robert Haas pushed: - Doc clarification for synchronous_commit. Fujii Masao http://git.postgresql.org/pg/commitdiff/37e666b8b5999fddd556138edd17a5f26384460f - Fix various infelicities in node functions. Mostly, this consists of adding support for fields which exist in the structure but aren't handled by copy/equal/outfuncs; but the create foreign table case can actually produce garbage output. Noah Misch http://git.postgresql.org/pg/commitdiff/53bbc681ca97650a4b8ea59d8f1710196654fca5 - Fix copyfuncs/equalfuncs support for ReassignOwnedStmt. Noah Misch http://git.postgresql.org/pg/commitdiff/b5eccaef2c05fd0c17f4510001528232b242a88e - Fix incorrect comment in SetBufferCommitInfoNeedsSave(). Noah Misch spotted the fact that the old comment is in fact incorrect, due to memory ordering hazards. http://git.postgresql.org/pg/commitdiff/ab77b2da8bf2cd1c8068f2f90e95c42d426aba3c - After PageSetAllVisible, use MarkBufferDirty. Previously, we used SetBufferCommitInfoNeedsSave, but that's really intended for dirty-marks we can theoretically afford to lose, such as hint bits. As for 9.2, the PD_ALL_VISIBLE mustn't be lost in this way, since we could then end up with a heap page that isn't all-visible and a visibility map page that is all visible, causing index-only scans to return wrong answers. http://git.postgresql.org/pg/commitdiff/e93c0b820f03e96ae0549cd30805ae734e5d5e2f - Tighten up error recovery for fast-path locking. The previous code could cause a backend crash after BEGIN; SAVEPOINT a; LOCK TABLE foo (interrupted by ^C or statement timeout); ROLLBACK TO SAVEPOINT a; LOCK TABLE foo, and might have leaked strong-lock counts in other situations. Report by Zoltán Böszörményi; patch review by Jeff Davis. http://git.postgresql.org/pg/commitdiff/53c5b869b464d567c3b8f617201b49a395f437ab - Finish rename of FastPathStrongLocks to FastPathStrongRelationLocks. Commit 8e5ac74c1249820ca55481223a95b9124b4a4f95 tried to do this renaming, but I relied on gcc to tell me where I needed to make changes, instead of grep. Noted by Jeff Davis. http://git.postgresql.org/pg/commitdiff/4a6fab03f23ed15f33e607b321c339d0c96c6b58 - Remove bogus comment from HeapTupleSatisfiesNow. This has been wrong for a really long time. We don't use two-phase locking to protect against serialization anomalies. Per discussion on pgsql-hackers about 2011-03-07; original report by Dan Ports. http://git.postgresql.org/pg/commitdiff/293ec33c32e8e20fcb5859885a4b37ff6d855240 Tom Lane pushed: - Revise parameterized-path mechanism to fix assorted issues. This patch adjusts the treatment of parameterized paths so that all paths with the same parameterization (same set of required outer rels) for the same relation will have the same rowcount estimate. We cache the rowcount estimates to ensure that property, and hopefully save a few cycles too. Doing this makes it practical for add_path_precheck to operate without a rowcount estimate: it need only assume that paths with different parameterizations never dominate each other, which is close enough to true anyway for coarse filtering, because normally a more-parameterized path should yield fewer rows thanks to having more join clauses to apply. In add_path, we do the full nine yards of comparing rowcount estimates along with everything else, so that we can discard parameterized paths that don't actually have an advantage. This fixes some issues I'd found with add_path rejecting parameterized paths on the grounds that they were more expensive than not-parameterized ones, even though they yielded many fewer rows and hence would be cheaper once subsequent joining was considered. To make the same-rowcounts assumption valid, we have to require that any parameterized path enforce *all* join clauses that could be obtained from the particular set of outer rels, even if not all of them are useful for indexing. This is required at both base scans and joins. It's a good thing anyway since the net impact is that join quals are checked at the lowest practical level in the join tree. Hence, discard the original rather ad-hoc mechanism for choosing parameterization joinquals, and build a better one that has a more principled rule for when clauses can be moved. The original rule was actually buggy anyway for lack of knowledge about which relations are part of an outer join's outer side; getting this right requires adding an outer_relids field to RestrictInfo. http://git.postgresql.org/pg/commitdiff/5b7b5518d0ea56c422a197875f7efa5deddbb388 - Adjust join_search_one_level's handling of clauseless joins. For an initial relation that lacks any join clauses (that is, it has to be cartesian-product-joined to the rest of the query), we considered only cartesian joins with initial rels appearing later in the initial-relations list. This creates an undesirable dependency on FROM-list order. We would never fail to find a plan, but perhaps we might not find the best available plan. Noted while discussing the logic with Amit Kapila. Improve the comments a bit in this area, too. Arguably this is a bug fix, but given the lack of complaints from the field I'll refrain from back-patching. http://git.postgresql.org/pg/commitdiff/1f0363001166ef6a43619846e44cfb9dbe7335ed - Use fuzzy not exact cost comparison for the final tie-breaker in add_path. Instead of an exact cost comparison, use a fuzzy comparison with 1e-10 delta after all other path metrics have proved equal. This is to avoid having platform-specific roundoff behaviors determine the choice when two paths are really the same to our cost estimators. Adjust the recently-added test case that made it obvious we had a problem here. http://git.postgresql.org/pg/commitdiff/33e99153e93b9accfa51ac036828144e1c2507b7 Alvaro Herrera pushed: - Recast "ONLY" column CHECK constraints as NO INHERIT. The original syntax wasn't universally loved, and it didn't allow its usage in CREATE TABLE, only ALTER TABLE. It now works everywhere, and it also allows using ALTER TABLE ONLY to add an uninherited CHECK constraint, per discussion. The pg_constraint column has accordingly been renamed connoinherit. This commit partly reverts some of the changes in 61d81bd28dbec65a6b144e0cd3d0bfe25913c3ac, particularly some pg_dump and psql bits, because now pg_get_constraintdef includes the necessary NO INHERIT within the constraint definition. Author: Nikhil Sontakke. Some tweaks by me http://git.postgresql.org/pg/commitdiff/09ff76fcdb275769ac4d1a45a67416735613d04b == Rejected Patches (for now) == No one was disappointed this week :-) == Pending Patches == Heikki Linnakangas sent in a patch to fix some infelicities in localized error context messages. Etsuro Fujita sent in another revision of the patch to validate file_fdw tables for not-NULL constraints. Kyotaro HORIGUCHI sent in three revisions of a fix for a bug where the checkpointer on hot standbys runs without looking checkpoint_segments. Fujii Masao sent in another fixing an infelicity in the last. Noah Misch sent in a patch to fix an issue where {ts,array}_typanalyze consumed much more memory than needed. Jameison Martin sent in a patch to optimize the case of tables with large numbers of columns, truncating the NULL bitmap at the last non-NULL column. Alexander Shulgin sent in two more revisions of a patch to add libpq URIs to the regression tests. Alvaro Herrera sent in a patch to add ALTER EXTENSION ... OWNED. Robert Haas sent in a patch to fix a bug in lazy_scan_heap() that could cause index-only scans to give wrong results. Laurenz Albe sent in a patch to fix a place where foreign table scan estimates were frozen at 1000 rows, independent of statistics gathered on same. Noah Misch sent in a patch to fix an issue in B-tree page deletion. Jan Urbanski sent in a patch to fix an issue with PL/PythonU triggers on composite-type columns. columns ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: pgsql-announce-unsubscribe&lt; at &gt;postgresql.org </pre> David Fetter 2012-04-23T06:34:56 pgpool-II 3.1.3 and 3.0.7 released http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2023 <pre>pgpool Global Development Group is pleased to announce the availability of pgpool-II 3.1.3 and 3.0.7 which are the latest stable versions of each major series. You can download the source codes from: http://www.pgpool.net/download.php?f=pgpool-II-3.1.3.tar.gz http://www.pgpool.net/download.php?f=pgpool-II-3.0.7.tar.gz ========================================================================= pgpool-II 3.1.3 ========================================================================= This is a bugfix release against pgpool-II 3.1.2. ------------------------------------------------------------------------- * Bug fixes ------------------------------------------------------------------------- - Add m4 files. This should prevent compiling problem on older OS's. (Tatsuo Ishii) - Fix to handle failover properly in detect_postmaster_down_error(). (Tatsuo Ishii) It is possible that it fails to read backend socket after detecting backend errors and before actually detaching the backend. - Fix bug that the process exits before unlocking semaphore by a signal interrupt. (Tatsuo Ishii) - Fix a memory leak in case of reset_query. (Tatsuo Ishii) - Fix pool_ssl_read() to deal with large data reading. (Tatsuo Ishii) Original complain is here: http://www.pgpool.net/pipermail/pgpool-general/2012-March/000299.html - Fix deadlock by enabling log_destination = syslog. (Tatsuo Ishii) Reported in bug tracker http://www.pgpool.net/mantisbt/view.php?id=9. Patch provided by Gilles Darold. - Allow to use multi statement in master/slave mode. (Tatsuo Ishii) From 3.1 transactional statements such as "BEGIN" are sent to not only primary but also standbys. This brings an unfortunate side effect: if the multi statement is "BEGIN;DELETE FROM table;END", this will be sent to standy as well and cause an error because standby does notallow write SQL. So fix is, if a query is a multi statement one, then send it to primary only. - Allow to have private cache of master node id. (Tatsuo Ishii) When master goes down running pgpool children look into NULL pointer because the process does not connect to the new master yet. The private cache returns the old master node id and will avoid the situation. Per bug reported in http://www.pgpool.net/mantisbt/view.php?id=51 - Fix pool_start_query() so that it uses my_master_node_id instead of REAL_MASTER_NODE_ID for initial virtual_master_node_id. (Tatsuo Ishii) Real master node could be changed while pgpool is running in streaming replication mode. Previously it is assigned REAL_MASTER_NODE_ID, which could have no connections after fail over and cause segafult. - Fix pool_setall_node_to_be_sent() to use private_backend_status instead of BACKEND_INFO macro. (Tatsuo Ishii) It is possible that while processing, the node returned by BACKEND_INFO is not usable any more. - Fix failover(). (Tatsuo Ishii) Before it only restarts worker child only when pgpool child do not need restart. This is wrong. We need to restart worker child in any case. Otherwise it continues to send replication time lag check request to down the node. - Fix debug log message so that it does not contain null characters. (Toshihiro Kitagawa) - Fix SimpleQuery() so that it restores parser memory context when: 1) Builtin show commands are used 2) Parallel query mode 3) Query cache is used (Tatsuo Ishii) - Fix hangup when PREPARE statement causes error. (Toshihiro Kitagawa) This issue was reported by Tomonari Katsumata: Subject: [pgpool-general: 121] question of pgpool's behavior - Add doc/pgpool-fr.html to Makefile.am. (Tatsuo Ishii) This had been forgotten when the doc was added. - Fix hangup during md5 authentication that occurs in daemon mode and log_destination is 'syslog'. (Yugo Nagata) Reported in bug tracker http://www.pgpool.net/mantisbt/view.php?id=2. ========================================================================= pgpool-II 3.0.7 ========================================================================= This is a bugfix release against pgpool-II 3.0.6. ------------------------------------------------------------------------- * Bug fixes ------------------------------------------------------------------------- - Add m4 files. This should prevent compiling problem on older OS's. (Tatsuo Ishii) - Fix bug that the process exits before unlocking semaphore by a signal interrupt. (Tatsuo Ishii) - Fix a memory leak in case of reset_query. (Tatsuo Ishii) - Fix SimpleQuery() so that it restores parser memory context when: 1) Builtin show commands are used 2) Parallel query mode 3) Query cache is used (Tatsuo Ishii) - Fix pool_ssl_read() to deal with large data reading. (Tatsuo Ishii) Original complain is here: http://www.pgpool.net/pipermail/pgpool-general/2012-March/000299.html - Fix hangup when PREPARE statement causes error. (Toshihiro Kitagawa) This issue was reported by Tomonari Katsumata: Subject: [pgpool-general: 121] question of pgpool's behavior ========================================================================= </pre> Yugo Nagata 2012-04-23T06:25:37 PgNext: Cancelled http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2022 <pre> 04/18/2012 PostgreSQL Conference Next 2012, in Denver from Jun 26th - 29th is cancelled. If you are looking for another conference in this time frame we suggest: http://www.pgcon.org/ There are also other conferences coming up in the next 6 months: http://www.postgresopen.org/ http://www.pgconf.eu Lastly, there is a Denver PgDay in October. PgDay's are a great way to meet locals and enjoy a smaller community setting but still maintain top notch content. Sincerely, Joshua D. Drake </pre> Joshua D. Drake 2012-04-18T18:50:37 Re: PgBouncer 1.5.1 http://permalink.gmane.org/gmane.comp.db.postgresql.announce/2021 <pre>[Re-reply to keep -announce in the loop..] On Wed, Apr 18, 2012 at 12:42 AM, Mark Felder &lt;feld&lt; at &gt;feld.me&gt; wrote: The .tar.gz on pgfoundry.org looks OK, so this must be some local problem. </pre> Marko Kreen 2012-04-18T14:07:34 Search Engine Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.db.postgresql.announce