Skip site navigation (1) Skip section navigation (2)

== Wöchentlicher PostgreSQL Newsletter - 03. Oktober 2010 ==

From: Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de>
To: "pgsql-de-allgemein(at)postgresql(dot)org" <pgsql-de-allgemein(at)postgresql(dot)org>
Cc: "pgusers(at)postgres(dot)de" <pgusers(at)postgres(dot)de>
Subject: == Wöchentlicher PostgreSQL Newsletter - 03. Oktober 2010 ==
Date: 2010-10-04 23:01:17
Message-ID: 4CAA5CBD.5060703@wars-nicht.de (view raw or flat)
Thread:
Lists: pgsql-de-allgemein

Der Originalartikel befindet sich unter:

http://www.postgresql.org/community/weeklynews/pwn20101003



== Wöchentlicher PostgreSQL Newsletter - 03. Oktober 2010 ==

PgDay.IT 2010 wird am 10. Dezember in Rom stattfinden. Der Call for
Papers ist jetzt offen.
http://www.pgday.it/

Die Vorträge für JDCon West sind jetzt online.
https://www.postgresqlconference.org/2010/west/talks

Michael Renner wird einen Vortrag über Datenbankreplikation mit 
PostgreSQL 9.0
am 12. Oktober im Metalab in Wien, Österreich halten. Link & Informationen
in de_AT:
http://metalab.at/wiki/PostgreSQL_repliziert_9.0

== PostgreSQL Produkt Neuigkeiten ==

Another PostgreSQL Diff Tool 2.1, ein Werkzeug um Datenbankdiffs
zu erstellen, ist erschienen.
http://apgdiff.startnet.biz/

phpPgAdmin 5.0-beta2, ein webbasiertes Administrationstool für
PostgreSQL, ist erschienen.
http://phppgadmin.sourceforge.net/

== PostgreSQL Lokal ==

Frühbucherregistrierung für JDCon West 2010 ist jetzt möglich.
https://www.postgresqlconference.org/content/pgwest-2010-registration

Der Call for Papers für den PGDay.EU 2010 am 6.-8. Dezember in
Stuttgart ist nun eröffnet.
http://2010.pgday.eu/callforpapers

== PostgreSQL in den News ==

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

Dieser wöchentliche PostgreSQL Newsletter wurde erstellt von David Fetter.

Sende Neuigkeiten und Ankündigungen bis Sonntag, 15 Uhr Pazifischer
Zeit. Bitte sende englische Beiträge an david(at)fetter(dot)org, deutsche an
pwn(at)pgug(dot)de, italienische an pwn(at)itpug(dot)org(dot)

== Reviews ==

Dean Rasheed reviewed Andrew Dunstan's patch to extend ENUMs.

Hitoshi Harada reviewed Pavel Stehule's patch to add median and
percentile functions, and suggested ways to implement them in the
context of windowing.

Peter Geoghegan reviewed and sent updated patches for the ISN patch
originally by Jan Otto.
== Applied Patches ==

Robert Haas pushed:

- Add "(change requires restart)" note to some postgresql.conf
   parameters.  Devrim GÜNDÜZ.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=2ce003973db82205cec55d596d51e957293019d1

- Add a SECURITY LABEL command.  This is intended as infrastructure to
   support integration with label-based mandatory access control
   systems such as SE-Linux. Further changes (mostly hooks) will be
   needed, but this is a big chunk of it.  KaiGai Kohei and Robert
   Haas.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=4d355a8336e0f2265b31d678ffd1ee5cf9e79fae

- Fix duplicate OIDs introduced by SECURITY LABEL patch.  Report by
   Shigeru Hanada.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=eacb22ec476a7bc49bdb2054a76a2b27a429a295

- Adjust pg_archivecleanup docs to match message changes made
   2010-06-17.  Erik Rijkers.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1f0eb5de9eb56a2eb71cc538f12861b084e7b03b

ITAGAKI Takahiro pushed:

- Add DISCARD to the command_no_begin list for AUTOCOMMIT=off.
   Backpatch to 8.3.  Reported by Sergey Burladyan.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=d08c698d9d47f9d004fd0bb6212ca80259e2fe9c

- Only DISCARD ALL should be in the command_no_begin list.  We allowes
   DISCARD PLANS and TEMP in a transaction.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=62b6aaa40b2abb26edf18d1cd00dffcac090f67a

Andrew Dunstan pushed:

- Fix MSVC builds for dummy_seclabel breakage.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f00847dc012e9c5219ef0e8e212d173d24700275

Alvaro Herrera pushed:

- In doc/src/sgml/ref/security_label.sgml, add missing agg_type
   nonterminal description in new reference page.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=3bb27fb503b421dae5c5d95d75842bbc048f2fab

Bruce Momjian pushed:

- Add mention of installing pg_upgrade_support in pg_upgrade doc
   section title, per suggestion from Ian Barwick.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=9c5f4f6cb50dd22028acc0b6f20291a5edcac62b

- Mention in pg_upgrade docs that the proper Win32 service name should
   be used.  Per report from Harald Armin Massa.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6b44b9ba56e02d63425a8d950ef141bb007745ff

- Mention that pg_upgrade requires write permission in the current
   directory.  Per report from Harald Armin Massa.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=ae9acb677950cf2afa037349b73fa3351d6e1d31

- Properly close files after read file failure to prevent potential
   resource leak.  Of course, any such failure aborts pg_upgrade, but
   might as well be clean about it.  Per patch from Grzegorz
   Jaskiewicz.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=f175884520949fbc52908d2f4b2baacde5906ebc

- Fix leak patch that was using fclose() instead of close().
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a1bb570de97c71eba3c1b7a067063e8ba28c41d5

- In pg_upgrade, properly handle oids > 2^31 by using strtoul()
   internally rather than atol().  Per report from Brian Hirt
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=9340fb80b1dba5528c0d16b24985369659a19377

- Use macro atooid() for conversion of strings to oids, per suggestion
   from Tom.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=807005c024aa57b5af729d021263cbf179fd5121

- Have pg_upgrade use strtoul(), not strtol().
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=fe61db6f0ceb508357bcddc39b388e2806cf11d0

Tom Lane pushed:

- Fix PlaceHolderVar mechanism's interaction with outer joins.  The
   point of a PlaceHolderVar is to allow a non-strict expression to be
   evaluated below an outer join, after which its value bubbles up like
   a Var and can be forced to NULL when the outer join's semantics
   require that.  However, there was a serious design oversight in
   that, namely that we didn't ensure that there was actually a correct
   place in the plan tree to evaluate the placeholder :-(.  It may be
   necessary to delay evaluation of an outer join to ensure that a
   placeholder that should be evaluated below the join can be evaluated
   there.  Per recent bug report from Kirill Simonov.  Back-patch to
   8.4 where the PlaceHolderVar mechanism was introduced.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=eb229505103eb5494c33832d422584bfdee03fc6

- Fix another small oversight in command_no_begin patch.  Need a
   "return false" to prevent tests from continuing after we've moved
   the "query" pointer.  As it stood, it'd accept "DROP DISCARD ALL" as
   a match.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=112c3fc6db62b39ded8965eddce1f4213308b957

- Fix incorrect usage of non-strict OR joinclauses in appendrel
   indexscans.  By chance I happened to notice that bug #5076 was still
   broken in the 8.3 branch, though it worked everywhere else.  The
   reason is that 8.3's version of adjust_appendrel_attrs_mutator
   neglected to adjust RestrictInfo.nullable_relids.  This was an
   oversight in my patch of 2009-04-16, which I apparently corrected in
   the later branches on 2009-08-13 without realizing that it affected
   the 8.3 branch as well.  By the time the bug report was filed, it
   was not reproducible in 8.4.  I don't recall if I wrote it off as
   already fixed, or it just fell through the cracks; but anyway it's
   been a live bug in 8.3 for a year.

- Improve messages for too many private files/dirs.  Per Alexey
   Parshin.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=5ac144d5c2906cc4b45423ac6575653a8df1b3d0

- Update release notes for releases 9.0.1, 8.4.5, 8.3.12, 8.2.18,
   8.1.22, 8.0.26, and 7.4.30.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a5683ea0423752cca323e528cb160273ad794054

- Fix back-branch breakage from ill-advised last-minute commit.

- Throw an appropriate error if ALTER COLUMN TYPE finds a dependent
   trigger.  Actually making this case work, if the column is used in
   the trigger's WHEN condition, will take some new code that probably
   isn't appropriate to back-patch.  For now, just throw a
   FEATURE_NOT_SUPPORTED error rather than allowing control to reach
   the "unexpected object" case.  Per bug #5688 from Daniel Grace.
   Back-patch to 9.0 where the possibility of such a dependency was
   introduced.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1f0b62e8c28026f5d1d3693087f7b4aef6a191af

- Remove excess argument to open(2).  Many compilers don't complain
   about this, but some do, and it's certainly wrong.  Back-patch to
   8.4 where the error was introduced.  Mark Kirkwood.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=e77f605d431c488983d6c96cb3513c691bf1907c

- Behave correctly if INSERT ... VALUES is decorated with additional
   clauses.  In versions 8.2 and up, the grammar allows attaching ORDER
   BY, LIMIT, FOR UPDATE, or WITH to VALUES, and hence to INSERT ...
   VALUES.  But the special-case code for VALUES in
   transformInsertStmt() wasn't expecting any of those, and just
   ignored them, leading to unexpected results.  Rather than complicate
   the special-case path, just ensure that the presence of any of those
   clauses makes us treat the query as if it had a general SELECT.  Per
   report from Hitoshi Harada.
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=3a13f12b3a18da0a61571cb134fdecea03a10d6f

Peter Eisentraut pushed:

- Update ecpglib error code listing.  Satoshi Nagayasu
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=fe48d9471eea6a5e8f8162bfed7d8f7c264904ab

- Add/fix caching on some configure checks
 
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=804a786c958d44fdf3b2e2d4774618f919759dc8

- Translation updates for 9.0.1, 8.4.5, 8.3.12, 8.2.18, 8.1.22,
   8.0.26, and 7.4.30.

Marc Fournier pushed:

- Tag 9.0.1, 8.4.5, 8.3.12, 8.2.18, 8.1.22, 8.0.26, and 7.4.30.

== Abgelehnte Patches (bis jetzt) ==

No one was disappointed this week :-)

== Eingesandte Patches ==

Tom Lane sent in a patch to fix a bug in subquery JOIN ordering.

ITAGAKI Takahiro sent in another revision of the patch to make CLUSTER
operations more efficient.

Grzegorz Jaskiewicz sent in a patch to fix an issue where it's
possible to dereference a null pointer in byteaout().

Greg Smith sent in an updated version of Boxuan Zhai's patch to
implement MERGE.

Bernd Helmle sent in an updated revision of the patch to add triggers
to views.

Pavel Stehule sent in another revision of the patch to add formatting
functions.

Fujii Masao sent in another revision of the patch to change libpq for
synchronous replication.

Andrew Dunstan sent in another revision of the patch to extend ENUMs.

Robert Haas sent in another revision of the patch to implement
merge-append.

Gurjeet Singh sent in a patch to allow people to replace a primary key
with another index.

Pavel Stehule sent in three revisions of a patch to add FOR...IN
[array] to PL/pgsql.

Pavel Stehule sent in a patch to implement a subscripts function.

Gregory Stark sent in a patch to add gtrusage profiling to EXPLAIN
output.

Pavel Stehule sent in three more revisions of a patch to add median
and percentile functions.

Hitoshi Harada sent in another revision of the patch to add DML
(INSERT, UPDATE, DELETE) to the top level of CTEs.

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




pgsql-de-allgemein by date

Next:From: Andreas 'ads' ScherbaumDate: 2010-10-10 13:43:50
Subject: PGDay.EU 2010 Call for Papers endet bald!
Previous:From: Tim LandscheidtDate: 2010-10-04 18:03:30
Subject: "Folgen" mit "Lücken"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group