== Wöchentlicher PostgreSQL Newsletter - 20. März 2011 ==

== Wöchentlicher PostgreSQL Newsletter - 20. März 2011 ==

am 21.03.2011 23:40:33 von adsmail

Der Originalartikel befindet sich unter:


== Wöchentlicher PostgreSQL Newsletter - 20. März 2011 ==

PostgreSQL wurde als Mentor Organisation für den Google Summer
of Code 2011 akzeptiert! Wenn du ein Student bist und ein
Projekt einreichen möchtest, das ist bis zum 28. März 2011
möglich. Details und Ideen für Projekte findest du hier:

== PostgreSQL Produkt Neuigkeiten ==

bucardo 4.4.2, ein PostgreSQL Replikationssystem,
ist erschienen:

tail_n_mail 1.17.6, ein Logfile Alarmwerkzeug ist erschienen:

== PostgreSQL Jobs im März ==

http://archives.postgresql.org/pgsql-jobs/2011-03/threads.ph p

== PostgreSQL Lokal ==

PostgreSQL Conference East 2011: New York,
vom 22. bis 25. März

Es wird eine umfangreiche PostgreSQL Präsenz auf der MySQL Konferenz
und Expo am am 11-14. April 2011 in Santa Clara, Kalifornien, geben.
http://en.oreilly.com/mysql2011/public/schedule/tag/postgres ql

Das Open Database Camp findet vom 7. bis 9. Mai 2011 in Sardinien,
Italien statt.
http://datacharmer.blogspot.com/2011/01/announcing-open-data base-camp-sardi=

PGCon findet am 19. und 20. Mai 2011 an der Universität
von Ottawa statt, vorher gibt es am 17. und 18. Mai
zwei Tage mit Trainings.

== PostgreSQL in den News ==

Planet PostgreSQL: http://planet.postgresql.org/

Dieser wöchentliche PostgreSQL Newsletter wurde erstellt von David Fet=

Sende Neuigkeiten und Ankündigungen bis Sonntag, 15 Uhr Pazifischer
Zeit. Bitte sende englische Beiträge an david@fetter.org, deutsche an
pwn@pgug.de, italienische an pwn@itpug.org, spanische an pwn@arpug.com.ar.

== Reviews ==

== Angewandte Patches ==

Bruce Momjian pushed:

- Remove duplicate time-based macros recently added.
http://git.postgresql.org/pg/commitdiff/b051a34fd8877635186e d84a857f2f38cd0=

- Add database comments to template0 and postgres databases, and
improve the comments on the template1 database. No catalog version
bump because they are just comments.
http://git.postgresql.org/pg/commitdiff/ddd6ff289f2512f88149 3b7793853a96955=

- Wording adjustment for restart_after_crash entry Specifically,
mention that "restart" is disabled by this parameter.
http://git.postgresql.org/pg/commitdiff/df4a9595c20ccd3d3b4c e0e638ca1a5e825=

- Fix spelling error in fuzzystrmatch docs.
http://git.postgresql.org/pg/commitdiff/b774efa9d57a02fbd64d afbe55a059253fb=

- Add hint suggesting the use of EXECUTE CREATE TABLE ... AS for
http://git.postgresql.org/pg/commitdiff/2b8364de698b0b425e5d 8631a63c91387ee=

- Adjust doc wording about the casting exceptions for composite types.
http://git.postgresql.org/pg/commitdiff/a858ca19df1491a50828 64335efb0fe08e2=

- Remove unused copy_dir() function from pg_upgrade.
http://git.postgresql.org/pg/commitdiff/898a14e1a0ba845c957f 42f205495af932f=

- Document guc context values, and reference them from the config doc
section. Tom Lane.
http://git.postgresql.org/pg/commitdiff/e148443ddd95cd29edf4 cc1de6188eb9cee=

- Document the all-balls IPv6 address.
http://git.postgresql.org/pg/commitdiff/a7136b7fa2505ec20921 0803bb74a7946ed=

- Document that the timestamp returned by
pg_last_xact_replay_timestamp is the time on the primary that the
transaction was generated.
http://git.postgresql.org/pg/commitdiff/0191e120e6b427f16aed 239c657b9e32c83=

- Remove "all balls" mention of network address; change IPv6 address
to ::/0.
http://git.postgresql.org/pg/commitdiff/56bb7f2a0275c5e7f17f 8fba0d93d12a471=

- Initial version of PostgreSQL 9.1 release notes.
http://git.postgresql.org/pg/commitdiff/b03b17c4118345cc89dd a1d96cda9ed2313=

- Add SGML markup for keywords, terms, functions, commands, etc.
http://git.postgresql.org/pg/commitdiff/025f4c72f029242a6aaf 3f14bb6d7da4ce0=

- Add links to documentation from 9.1 release notes.
http://git.postgresql.org/pg/commitdiff/b2c5b3d1753f1a3e5cb6 8a610bda27ad768=

- Move PITR and StreamingRep up one level of heading in the 9.1
release notes. Remove excessive linking to pg_ctl manual page.
Reorder incompatibility sections.
http://git.postgresql.org/pg/commitdiff/c2f4ea469b52e6f7fedf f651a4aa0acced8=

- Reorder some 9.1 release item documentation entries, fix some
awkward wording.
http://git.postgresql.org/pg/commitdiff/f670c195b64a97b8b9e9 780e80614cd03b9=

- Fix snapshot isolation level typo in 9.1 release notes. Thom Brown
http://git.postgresql.org/pg/commitdiff/e8f4c240c7065edcbe82 e06a2d86c05c8ab=

- Another 9.1 release note typo fix.
http://git.postgresql.org/pg/commitdiff/78fce29628f99a7dd002 561dc87904456c9=

- Markup and wording improvements for 9.1 release notes.
http://git.postgresql.org/pg/commitdiff/62bf9c28061c614df530 ac672b1e59f88e8=

Tom Lane pushed:

- Adjust regression test to avoid platform-dependent failure. We have
a test that verifies that max(anyarray) will cope if the array
column elements aren't all the same array type. However, it's now
possible for that to produce a collation-related error message
instead of the expected one, if the first two column elements happen
to be of the same type and it's one that expects to be given
collation info. Tweak the test to ensure this doesn't happen. Per
buildfarm member pika.
http://git.postgresql.org/pg/commitdiff/f12423d75a1181d75bd6 46869b140ba0c19=

- Improve handling of unknown-type literals in UNION/INTERSECT/EXCEPT.
This patch causes unknown-type Consts to be coerced to the resolved
output type of the set operation at parse time. Formerly such
Consts were left alone until late in the planning stage. The
disadvantage of that approach is that it disables some
optimizations, because the planner sees the set-op leaf query as
having different output column types than the overall set-op. We
saw an example of that in a recent performance gripe from Claudio
Freire. Fixing such a Const requires scribbling on the leaf query
in transformSetOperationTree, but that should be all right since if
the leaf query's semantics depended on that output column, it would
already have resolved the unknown to something else. Most of the
bulk of this patch is a simple adjustment of
transformSetOperationTree's API so that upper levels can get at the
TargetEntry containing a Const to be replaced: it now returns a list
of TargetEntries, instead of just the bare expressions.
http://git.postgresql.org/pg/commitdiff/72cfc17aef4fc9aa2de1 c82045b7d609c0f=

- Revise collation derivation method and expression-tree
representation. All expression nodes now have an explicit
output-collation field, unless they are known to only return a
noncollatable data type (such as boolean or record). Also, nodes
that can invoke collation-aware functions store a separate field
that is the collation value to pass to the function. This avoids
confusion that arises when a function has collatable inputs and
noncollatable output type, or vice versa. Also, replace the
parser's on-the-fly collation assignment method with a post-pass
over the completed expression tree. This allows us to use a more
complex (and hopefully more nearly spec-compliant) assignment rule
without paying for it in extra storage in every expression node.
Fix assorted bugs in the planner's handling of collations by making
collation one of the defining properties of an EquivalenceClass and
by converting CollateExprs into discardable RelabelType nodes during
expression preprocessing.
http://git.postgresql.org/pg/commitdiff/b310b6e31ce5aa9e456c 43c0e8e93248b0c=

- Fix up handling of C/POSIX collations. Install just one instance of
the "C" and "POSIX" collations into pg_collation, rather than one
per encoding. Make these instances exist and do something useful
even in machines without locale_t support: to wit, it's now possible
to force comparisons and case-folding functions to use C locale in
an otherwise non-C database, whether or not the platform has support
for using any additional collations. Fix up severely broken
upper/lower/initcap functions, too: the C/POSIX fastpath now does
what it is supposed to, and non-default collations are handled
correctly in single-byte database encodings. Merge the two separate
collation hashtables that were being maintained in pg_locale.c, and
be more wary of the possibility that we fail partway through filling
a cache entry.
http://git.postgresql.org/pg/commitdiff/176d5bae1d636fc1e918 40b12cbd04c96d6=

- Suppress platform-dependent unused-variable warning. The local
variable "sock" can be unused depending on compilation flags. But
there seems no particular need for it, since the kernel calls can
just as easily say port->sock instead.
http://git.postgresql.org/pg/commitdiff/82e4d45bd0ba9c07b8a9 7f28f939db6d8d5=

- Add some platform-independent tests for the collation feature.
There's a lot we can't test very well without platform dependencies,
but the C/POSIX collations should now work the same way everywhere.
http://git.postgresql.org/pg/commitdiff/9b095fbea4d6e80e3288 e08bd2af4f33aa6=

Magnus Hagander pushed:

- Remove special case allowing parameters to ident auth for initdb.
This was required in pre-8.4 versions to allow the specification of
"ident sameuser", but sameuser is no longer required. It could be
extended to allow all parameters in the future, but should then
apply to all methods and not just ident.
http://git.postgresql.org/pg/commitdiff/01c1a12a5bb4d4f837a5 42c187ebb2719f9=

- Properly clear the verbose output of pg_basebackup. Don't leave
partial filename information on the last status or dangling
characters if the previous filename was longer than the current one.
http://git.postgresql.org/pg/commitdiff/4a0014806d909bbb490f 568af0b8f1ede06=

- Rename ident authentication over local connections to peer. This
removes an overloading of two authentication options where one is
very secure (peer) and one is often insecure (ident). Peer is also
the name used in libpq from 9.1 to specify the same type of
authentication. Also make initdb select peer for local connections
when ident is chosen, and ident for TCP connections when peer is
chosen. ident keyword in pg_hba.conf is still accepted and maps to
peer authentication.
http://git.postgresql.org/pg/commitdiff/6f9192df61e183826211 ad2eaf325c6de5c=

- Misc minor fixes to 9.1 release notes. Thom Brown
http://git.postgresql.org/pg/commitdiff/0f96ae643c5815d14e39 ae8d349be218aae=

Robert Haas pushed:

- Remove 13 keywords that are used only for ROLE options. Review by
Tom Lane.
http://git.postgresql.org/pg/commitdiff/5ca4dfc79f21828174de 3a8bc7d29718d0c=

- Minor sync rep documentation improvements: Make the name of the ID
tag for the GUC entry match the GUC name; Clarify that
synchronous_replication waits for xlog flush, not receipt; Mention
that synchronous_replication won't wait if max_wal_senders=3D0.
http://git.postgresql.org/pg/commitdiff/f0f3617135854281bdb7 9179a895c102d54=

- Corrections to CREATE FOREIGN TABLE documentation. Omit incorrect =3D
sign, and properly document server_name parameter. Shigeru Hanada.
http://git.postgresql.org/pg/commitdiff/5f588e20051eb18333f6 ea5b46bd779ba1e=

- Tab completion for \pset format and \pset linestyle. Pavel Stehule
http://git.postgresql.org/pg/commitdiff/ad3aff45f0d302b35d00 9e525de8a9d0ee9=

- Tab completion for \pset format and \pset linestyle. Pavel Stehule
http://git.postgresql.org/pg/commitdiff/ad3aff45f0d302b35d00 9e525de8a9d0ee9=

- Fix various possible problems with synchronous replication. 1.
Don't ignore query cancel interrupts. Instead, if the user asks to
cancel the query after we've already committed it, but before it's
on the standby, just emit a warning and let the COMMIT finish. 2.
Don't ignore die interrupts (pg_terminate_backend or fast shutdown).
Instead, emit a warning message and close the connection without
acknowledging the commit. Other backends will still see the effect
of the commit, but there's no getting around that; it's too late to
abort at this point, and ignoring die interrupts altogether doesn't
seem like a good idea. 3. If synchronous_standby_names becomes
empty, wake up all backends waiting for synchronous replication to
complete. Without this, someone attempting to shut synchronous
replication off could easily wedge the entire system instead. 4.
Avoid depending on the assumption that if a walsender updates
MyProc->syncRepState, we'll see the change even if we read it
without holding the lock. The window for this appears to be quite
narrow (and probably doesn't exist at all on machines with strong
memory ordering) but protecting against it is practically free, so
do that. 5. Remove useless state SYNC_REP_MUST_DISCONNECT, which
isn't needed and doesn't actually do anything. There's still some
further work needed here to make the behavior of fast shutdown
plausible, but that looks complex, so I'm leaving it for a separate
commit. Review by Fujii Masao.
http://git.postgresql.org/pg/commitdiff/9a56dc3389b9470031e9 ef8e45c95a68098=

- Add pause_at_recovery_target to recovery.conf.sample; improve docs.
Fujii Masao, but with the proposed behavior change reverted, and the
rest adjusted accordingly.
http://git.postgresql.org/pg/commitdiff/84abea76f60c5fd1c008 b8ddf250b4bc89e=

- Remove bogus comment.
http://git.postgresql.org/pg/commitdiff/02b1f84e7d2c8921d3ef 291469cfd4b7235=

- Protocol documentation for Hot Standby feedback messages.
http://git.postgresql.org/pg/commitdiff/76dbb4615389e1f44e48 074b87be7726214=

- Minor fixes for high availability documentation. Erik Rijkers and
http://git.postgresql.org/pg/commitdiff/f94c6f9c0f05ff70b232 e620eb9c420294e=

- Remove bogus semicolons in recoveryPausesHere. Without this, the
startup process goes into a tight loop, consuming 100% of one CPU
and failing to respond to interrupts.
http://git.postgresql.org/pg/commitdiff/777e8c0015743224cc46 f3ce39243b05c6d=

- Remove ancient -X options to pg_dump, pg_dumpall, pg_restore. The
last version in which these options were documented is now EOL, so
it's time to get rid of them for real. We now use GNU-style long
options instead.
http://git.postgresql.org/pg/commitdiff/c5eb835bbffb99518405 a1e5bccb58c85e0=

- Make synchronous replication query cancel/die messages more
consistent. Per a gripe from Thom Brown about my previous commit in
this area, commit 9a56dc3389b9470031e9ef8e45c95a680982e01a.
http://git.postgresql.org/pg/commitdiff/7a37900443b016e0e7c7 2f6b42327bc05f8=

- Woops. Previous patch to remove -X options missed getopt_long
calls(). Noted by Tom Lane.
http://git.postgresql.org/pg/commitdiff/f78ba0a73a60f40270b2 1c4582f6a7d52fe=

- Move synchronous_standbys_defined updates from WAL writer to BG
writer. This is advantageous because the BG writer is alive until
much later in the shutdown sequence than WAL writer; we want to make
sure that it's possible to shut off synchronous replication during a
smart shutdown, else it might not be possible to complete the
shutdown at all. Per very reasonable gripes from Fujii Masao and
Simon Riggs.
http://git.postgresql.org/pg/commitdiff/727589995a3e027046f0 da7af6ba665b0b4=

- Fix possible "tuple concurrently updated" error in ALTER TABLE.
When adding an inheritance parent to a table, an AccessShareLock on
the parent isn't strong enough to prevent trouble, so take
ShareUpdateExclusiveLock instead. Since this is a behavior change,
albeit a fairly unobtrusive one, and since we have only one report
from the field, no back-patch. Report by Jon Nelson, analysis by
Alvaro Herrera, fix by me.
http://git.postgresql.org/pg/commitdiff/fbcf4b92aa64d4577bcf 25925b055316b97=

Andrew Dunstan pushed:

- Use correct PATH separator for Cygwin in pg_regress.c. This has
been broken for years, and I'm not sure why it has not been noticed
before, but now a very modern Cygwin breaks on it, and the fix is
clearly correct. Backpatching to all live branches.
http://git.postgresql.org/pg/commitdiff/5b079cb248b91cbd5bc5 77ea96802ec466f=

Peter Eisentraut pushed:

- Raise maximum value of several timeout parameters The maximum value
of deadlock_timeout, max_standby_archive_delay,
max_standby_streaming_delay, log_min_duration_statement, and
log_autovacuum_min_duration was INT_MAX/1000 milliseconds, which is
about 35min, which is too short for some practical uses. Raise the
maximum value to INT_MAX; the code that uses the parameters already
supports that just fine.
http://git.postgresql.org/pg/commitdiff/8c0a5eb78af00ec4720e 693feaba70b5a73=

Alvaro Herrera pushed:

- Fix PL/Python memory leak involving array slices. Report and patch
from Daniel Popowich, bug #5842 (with some debugging help from Alex
http://git.postgresql.org/pg/commitdiff/1c249fcfcc331d589a2f a1574e16c0ef3d1=

== Abgelehnte Patches (bis jetzt) ==

No one was disappointed this week :-)

== Eingesandte Patches ==

Fujii Masao sent in another revision of the replication server timeout

Robert Haas sent in two revisions of a patch intended to fix some
infelicities in syncrep.

Roman Zotov sent in a patch to turn PREFERRED for type from a boolean
to an int2, which allows for an expression of precedence.

Thom Brown sent in a patch to allow users to set a default database
name other than postgres in initdb.

Piyush Newe sent in a patch intended to fix some infelicities in
century handling in to_date.

Heikki Linnakangas sent in another revision of the patch to enable
taking multiple base backups.

Radoslaw Smogura sent in two revisions of a patch to add a second
level buffer cache.

Kevin Grittner sent in two revisions of a patch intended to fix an
issue in SSI.

Nikhil Sontakke sent in two revisions of a patch to fix an issue with
a VACUUM FULL deadlock.

Jan Urbanski sent in another revision of the patch to add PL/PythonU

Andreas 'ads' Scherbaum
Deutsche PostgreSQL User Group: http://www.pgug.de/
DPWN: http://andreas.scherbaum.la/blog/categories/18-PWN

Sent via pgsql-de-allgemein mailing list (pgsql-de-allgemein@postgresql.org)
To make changes to your subscription: