|From:||David Fetter <david-AT-fetter.org>|
|To:||PostgreSQL Announce <pgsql-announce-AT-postgresql.org>|
|Subject:||[ANNOUNCE] == PostgreSQL Weekly News - May 08 2011 ==|
|Date:||Sun, 8 May 2011 22:10:36 -0700|
== PostgreSQL Weekly News - May 08 2011 == PostgreSQL 9.1 beta 1 is out. Test! http://www.postgresql.org/developer/beta AustinPUG will meet on May 11 at 7 p.m in Austin, Texas, USA. Free Pizza! To get fed, RSVP to <austinpug AT postgresql DOT org>. http://pugs.postgresql.org/austinpug CHAR(11), the PostgreSQL Conference on Clustering, High Availability and Replication is now open for online registration and bookings. July 11-12 2011 in Cambridge, UK. http://www.char11.org/ PostgreSQL Confernece West (#PgWest) will be held September 27th-30th, 2011 at the San Jose Convention center in San Jose, California, USA. http://www.postgresqlconference.org == PostgreSQL Product News == pgbuildfarm client 4.5 released. http://pgfoundry.org/forum/forum.php?forum_id=1833 pgpool-II 3.1.0 alpha2, a connection pooler and more, released. http://pgfoundry.org/projects/pgpool/ == PostgreSQL Jobs for May == http://archives.postgresql.org/pgsql-jobs/2011-05/threads... == PostgreSQL Local == PGCon will be May 19-20, 2011 at the University of Ottawa, preceded by two days of tutorials on May 17-18. http://www.pgcon.org/2011/ PG Session 2, on PostGIS, will be held on June 23rd in Paris. The CfP is open! http://www.postgresql-sessions.org/en/2/ PostgreSQL Conference Europe 2011 will be held on October 18-21 in Amsterdam. http://2011.pgconf.eu/ pgbr will be in Sao Paulo, Brazil November 3-4, 2011. http://pgbr.postgresql.org.br/ == 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 email@example.com, German language to firstname.lastname@example.org, Italian language to email@example.com. Spanish language to firstname.lastname@example.org. == Reviews == == Applied Patches == Tom Lane pushed: - Improve aset.c's space management in contexts with small maxBlockSize. The previous coding would allow requests up to half of maxBlockSize to be treated as "chunks", but when that actually did happen, we'd waste nearly half of the space in the malloc block containing the chunk, if no smaller requests came along to fill it. Avoid this scenario by limiting the maximum size of a chunk to 1/8th maxBlockSize, so that we can waste no more than 1/8th of the allocated space. This will not change the behavior at all for the default context size parameters (with large maxBlockSize), but it will change the behavior when using ALLOCSET_SMALL_MAXSIZE. In particular, there's no longer a need for spell.c to be overly concerned about the request size parameters it uses, so remove a rather unhelpful comment about that. Merlin Moncure, per an idea of Tom Lane's http://git.postgresql.org/pg/commitdiff/6755558b92748287e... - Fix pull_up_sublinks' failure to handle nested pull-up opportunities. After finding an EXISTS or ANY sub-select that can be converted to a semi-join or anti-join, we should recurse into the body of the sub-select. This allows cases such as EXISTS-within-EXISTS to be optimized properly. The original coding would leave the lower sub-select as a SubLink, which is no better and often worse than what we can do with a join. Per example from Wayne Conrad. Back-patch to 8.4. There is a related issue in older versions' handling of pull_up_IN_clauses, but they're lame enough anyway about the whole area that it seems not worth the extra work to try to fix. http://git.postgresql.org/pg/commitdiff/dcc685debb02c507b... - Include unary plus in the Operator Precedence table. Per gripe from Grzegorz Szpetkowski. Also, change the subsection heading from "Lexical Precedence" (which is a contradiction in terms) to "Operator Precedence". http://git.postgresql.org/pg/commitdiff/671322751add80f33... - Remove precedence labeling of keywords TRUE, FALSE, UNKNOWN, and ZONE. These were labeled with precedences just to avoid attaching explicit precedences to the productions in which they were the last terminal symbol. Since a terminal symbol precedence marking can affect many other things too, it seems like better practice to attach precedence labels to the productions, and not mark the terminal symbols. Ideally we'd also remove the precedence attached to NULL_P, but it turns out that we are actually depending on that having a precedence higher than POSTFIXOP, else we get a shift/reduce conflict for postfix operators in b_expr. (Which more or less proves my point about these markings having a high risk of unexpected consequences.) For the moment, move NULL_P into the set of keywords grouped with IDENT, so that at least it will act similarly to non-keywords; and document the interaction. http://git.postgresql.org/pg/commitdiff/12b7164578e73abb0... - Move RegisterPredicateLockingXid() call to a safer place. The SSI patch inserted a call of RegisterPredicateLockingXid into GetNewTransactionId, which was a bad idea on a couple of grounds. First, it's not necessary to hold XidGenLock while manipulating that shared memory, and doing so is bad because XidGenLock is a high-contention lock that should be held for as short a time as possible. (Not to mention that it adds an entirely unnecessary deadlock hazard, since we must take SerializableXactHashLock as well.) Second, the specific place where it was put was between extending CLOG and advancing nextXid, which could result in unpleasant behavior in case of a failure there. Pull the call out to AssignTransactionId, which is much safer and arguably better from a modularity standpoint too. There is more work to do to clean up the failure-before-advancing-nextXid issue, but that is a separate change that will need to be back-patched. So for the moment I just want to make GetNewTransactionId look the same as it did in prior versions. http://git.postgresql.org/pg/commitdiff/d2088ae949993ad8e... - Fix some portability issues in isolation regression test driver. Remove random system #includes in favor of using postgres_fe.h. (The alternative to that is letting this module grow its own configuration testing ability...) Also fix the "make clean" target to actually clean things up. Per local testing. http://git.postgresql.org/pg/commitdiff/eff223ffd74eed268... Peter Eisentraut pushed: - Small cleanup of spacing in verbatim DocBook elements http://git.postgresql.org/pg/commitdiff/4b08bf8ce7a7515f6... - Fix alignment of --help output. Tabs replaced by spaces. http://git.postgresql.org/pg/commitdiff/ce2fc20071a6ae68e... - Message style cleanup http://git.postgresql.org/pg/commitdiff/bff074b1ab0dfed7a... - Remove redundant port number check. pg_basebackup doesn't need to police the format of port numbers. libpq already does that. http://git.postgresql.org/pg/commitdiff/7f1f1bfdbb199a003... - Link some tables into the surrounding text by their id http://git.postgresql.org/pg/commitdiff/a3b681f0bc46de6ae... - Improve pg_archivecleanup and pg_standby --help output. For consistency with other tools, put the options before further usage information. In pg_standby, remove the supposedly deprecated -l option from the given example invocation. http://git.postgresql.org/pg/commitdiff/b24181b26fc907583... - Improve formatting of pg_upgrade --help output. http://git.postgresql.org/pg/commitdiff/d6d823c8b0e6878cf... - Improve compiler string shown in version(). With some compilers such as Clang and ICC emulating GCC, using a version string of the form "GCC $version" can be quite misleading. Also, a great while ago, the version output from gcc --version started including the string "gcc", so it is redundant to repeat that. In order to support ancient GCC versions, we now prefix the result with "GCC " only if the version output does not start with a letter. http://git.postgresql.org/pg/commitdiff/8dd2ede3f82505c3f... Alvaro Herrera pushed: - Update some ALTER USER cross-references to ALTER ROLE. Greg Smith http://git.postgresql.org/pg/commitdiff/52897e54db1000f2f... - Add ID attribute to some sect2's missing it. David Fetter http://git.postgresql.org/pg/commitdiff/155743ad3108cd586... - Update obsolete mention of Sequoia, now known as Tungsten. Per http://joomla.aws.continuent.com/community/lab-projects/s... Greg Smith http://git.postgresql.org/pg/commitdiff/04be7ac271c4b6db6... - Improve description of read/write traffic scalability. Greg Smith, after a suggestion of James Bruce http://git.postgresql.org/pg/commitdiff/561485709673f4bc0... Bruce Momjian pushed: - Improve style of generate_history.pl Perl script. http://git.postgresql.org/pg/commitdiff/fb3ad7895ece674fc... - Adjust pg_upgrade FATAL error messages to have consistent newlines. Also adjust some error message capitalization for consistency. http://git.postgresql.org/pg/commitdiff/5c5f83507cb697e43... - Check that the pg_upgrade user specified is a super-user. Also report the error message when the post-pg_ctl connection fails. Per private bug report from EnterpriseDB. http://git.postgresql.org/pg/commitdiff/81301b85781245676... - In pg_upgrade, report non-super-user username in error message. http://git.postgresql.org/pg/commitdiff/1609ca5adb5c8b550... - Add missing documention connecting word. http://git.postgresql.org/pg/commitdiff/5293de580734bb16c... - Add xreflabels to /contrib manuals so links appear correct. Also update README.links to explain xref properly. http://git.postgresql.org/pg/commitdiff/e567c9ff3409203a3... - Add C comment why client encoding can be set in pg_upgrade. http://git.postgresql.org/pg/commitdiff/e6a740284291d1eba... - Add C comment about the fact that the autovacuum limit can go backwards by 3, but that is it OK. http://git.postgresql.org/pg/commitdiff/76e5b4c85d5d48308... Magnus Hagander pushed: - Clarify error message when attempting to create index on foreign table. Instead of just saying "is not a table", specifically state that indexes aren't supported on *foreign* tables. http://git.postgresql.org/pg/commitdiff/d76a149c955a6525c... - Unbreak the regression tests from my previous commit http://git.postgresql.org/pg/commitdiff/27525b183189487c6... Robert Haas pushed: - Fix typos in SECURITY LABEL documentation. KaiGai Kohei http://git.postgresql.org/pg/commitdiff/3ef5b2df9738fd079... - Add comment about memory reordering to PredicateLockTupleRowVersionLink. Dan Ports, per head-scratching from Simon Riggs and myself. http://git.postgresql.org/pg/commitdiff/71932ecc2b6ca0d74... == Rejected Patches (for now) == No one was disappointed this week :-) == Pending Patches == Gabriele Bartolini sent in another revision of the patch to smooth replication during VACUUM FULL. Joe Conway sent in a patch to fix clog redos under high load. Johann 'Myrkraverk' Oskarsson sent in a patch to fix an issue on mingw-w64 where the PGDLLEXPORT macro is blank. Alvaro Herrera updated the "preferred types" patch to HEAD. Jaime Casanova sent in a patch to add an xlogversion column to IDENTIFY_SYSTEM. This is one of the infrastructure pieces which will make on-line upgrades possible. Hitoshi Harada sent in a patch to allow the optimizer to pull up aggregate subqueries. Bruce Momjian sent in patches to adjust the comments on system tables. Magnus Hagander sent in a patch to fix the error for attempting to index a foreign table. Tom Lane sent in a patch to fix a some suprising precedence in PostgreSQL's SQL grammar. Dan Ports sent in two revisions of a patch to fix a race condition in SSI's ChecTargetForConflictsIn. Peter Geoghegan sent in a WIP patch to help save energy by waking up less frequently. Merlin Moncure sent in another revision of the patch to fix an issue between the visibility map and hint bits. Robert Haas sent in another revision of the patch to make visibility maps more crash-safe. Josh Kupershmidt sent in a patch to clean up psql's decribe.c. Andrew Dunstan sent in another revision of the patch to fix an issue where invalid characters were allowed in XML. Greg Smith sent in a patch exemplifying the idea of moving some contrib modules to being default, but still using the EXTENSION infrastructure. ---------------------------(end of broadcast)--------------------------- -To unsubscribe from this list, send an email to: email@example.com
Copyright © 2011, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds