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

== Wöchentlicher PostgreSQL Newsletter - 18. Oktober 2009 ==

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 - 18. Oktober 2009 ==
Date: 2009-10-19 16:10:24
Message-ID: 20091019181024.17b63c5e@iridium.wars-nicht.de (view raw or flat)
Thread:
Lists: pgsql-de-allgemein
Der Originalartikel befindet sich unter:

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



== Wöchentlicher PostgreSQL Newsletter - 18. Oktober 2009 ==

Commitfest 2009-09 ist beendet. Du kannst wieder anfangen, an deinen
eigenen Patches zu arbeiten :)

PostgreSQL Conference (JDCon) West endete heute. Danke an all die
wundervollen Leute in Seattle, die daraus einen Erfolg gemacht haben.

== PostgreSQL Produkt Neuigkeiten ==

PWN Translator 3.0, ein Übersetzungsskript für den
wöchentlichen PostgreSQL Newsletter, ist erschienen.
http://pgfoundry.org/projects/pwn-translation/

Benetl 3.2, ein ETL Werkzeug für Dateien, die PostgreSQL
nutzen, ist erschienen.
http://www.benetl.net

Bucardo 4.3.0, ein Replikationssystem mit Dual-Master
Kapazitäten, ist erschienen.
http://bucardo.org/wiki/Bucardo

== PostgreSQL Jobs im Oktober ==

http://archives.postgresql.org/pgsql-jobs/2009-10/threads.php

== PostgreSQL Lokal ==

PGCon Brasilien wird am 23.-24. Oktober 2009 auf dem Unicamp in
Campinas, Sao Paulo, stattfinden. Registrierung offen:
http://pgcon.postgresql.org.br/2009/

Federico Campoli wird einen PostgreSQL Vortrag auf der GULP (Linuxtag
Pisa) am 24. Oktober 2009 halten. Informationen auf italienisch unter:
http://linuxday2009.gulp.linux.it/

PGDay.EU 2009 wird an der Telecom ParisTech Universität in Paris,
Frankreich, am 6. und 7. November 2009 stattfinden.
http://www.pgday.eu/

OpenSQL Camp in Portland sucht Sponsoren. Bereite deine Reisepläne
jetzt vor! :)
http://www.chesnok.com/daily/2009/07/29/opensql-camp-comes-to-portland-november-14-15-2009/

Die 10. jährliche JPUG Konferenz findet am 20-21. November 2009 in
Tokio, Japan, statt.
http://archives.postgresql.org/pgsql-announce/2009-05/msg00018.php

FOSDEM 2010 findet am 6. und 7. Februar 2010 in Brüssel,
Belgien statt.
http://www.fosdem.org/

Die Chemnitzer Linuxtage finden am 13. und 14. März in
Chemnitz, Deutschland statt.
http://chemnitzer.linux-tage.de/

== 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)

== Angewandte Patches ==

Tom Lane committed:

- Move the handling of SELECT FOR UPDATE locking and rechecking out of
  execMain.c and into a new plan node type LockRows.  Like the recent
  change to put table updating into a ModifyTable plan node, this
  increases planning flexibility by allowing the operations to occur
  below the top level of the plan tree.  It's necessary in any case to
  restore the previous behavior of having FOR UPDATE locking occur
  before ModifyTable does.  This partially refactors EvalPlanQual to
  allow multiple rows-under-test to be inserted into the EPQ machinery
  before starting an EPQ test query.  That isn't sufficient to fix
  EPQ's general bogosity in the face of plans that return multiple
  rows per test row, though.  Since this patch is mostly about getting
  some plan node infrastructure in place and not about fixing
  ten-year-old bugs, I will leave EPQ improvements for another day.
  Another behavioral change that we could now think about is doing FOR
  UPDATE before LIMIT, but that too seems like it should be treated as
  a followon patch.

- Support GRANT/REVOKE ON ALL TABLES/SEQUENCES/FUNCTIONS IN SCHEMA.
  Petr Jelinek

- Use plurals (TABLES, FUNCTIONS, etc) in ALTER DEFAULT PRIVILEGES.
  We have the keywords as a consequence of the GRANT ALL patch, so we
  might as well use them and make the ALTER commands read more
  naturally.

- Code review for LIKE INCLUDING patch --- clean up some cosmetic and
  not so cosmetic stuff.

- In pgsql/src/backend/utils/adt/tsvector_op.c, fix ts_stat's failure
  on empty tsvector.  Also insert a couple of Asserts that check for
  stack overflow.  Bogus coding appears to be new in 8.4 --- older
  releases had a much simpler algorithm here.  Per bug #5111.

- Add "\pset linestyle ascii/unicode" option to psql, allowing our
  traditional ASCII-art style of table output to be upgraded to use
  Unicode box drawing characters if desired.  By default, psql will
  use the Unicode characters whenever client_encoding is UTF8.  The
  patch forces linestyle=ascii in pg_regress usage, ensuring we don't
  break the regression tests in Unicode locales.  Roger Leigh.

- Support SQL-compliant triggers on columns, ie fire only if certain
  columns are named in the UPDATE's SET list.  Note: the schema of
  pg_trigger has not actually changed; we've just started to use a
  column that was there all along.  catversion bumped anyway so that
  this commit is included in the history of potentially interesting
  changes to system catalog contents.  Itagaki Takahiro.

- In pgsql/src/pl/plpython/expected/plpython_unicode_0.out, first
  committed version of plpython_unicode_0.out did not actually contain
  the required \200 bytes.  Let's see if this commit works, or if CVS
  is messing it up.

- In pgsql/src/backend/libpq/auth.c, rewrite pam_passwd_conv_proc to
  be more robust: avoid assuming that the pam_message array contains
  exactly one PAM_PROMPT_ECHO_OFF message.  Instead, deal with however
  many messages there are, and don't throw error for PAM_ERROR_MSG and
  PAM_TEXT_INFO messages.  This logic is borrowed from openssh 5.2p1,
  which hopefully has seen more real-world PAM usage than we have.
  Per bug #5121 from Ryan Douglas, which turned out to be caused by
  the conv_proc being called with zero messages.  Apparently that is
  normal behavior given the combination of Linux pam_krb5 with MS
  Active Directory as the domain controller.  Patch all the way back,
  since this code has been essentially untouched since 7.4.
  (Surprising we've not heard complaints before.)

Andrew Dunstan committed:

- CREATE LIKE INCLUDING COMMENTS and STORAGE, and INCLUDING ALL
  shortcut. Itagaki Takahiro.

Alvaro Herrera committed:

- Add new PGC_S_DATABASE_USER enum value to several places missed by
  my patch last week.  Per note and patch from Jeff Davis.

- Avoid using trivial usernames in foreign_data regression test.
  Martin Pihlak.

Peter Eisentraut committed:

- In pgsql/doc/src/sgml/func.sgml, replace unmatched " by &quot; to
  avoid throwing off syntax highlighters.

- Add alternative expected file for unicode test for client encoding
  not UTF8.

- In the configure check for the Python distutils module, use a less
  obscure shell construct to hide away the stderr output.  Python 3.1
  actually core dumps on the current invocation
  (http://bugs.python.org/issue7111), but the new version also has the
  more general advantage of saving the error message in config.log for
  analysis.

Heikki Linnakangas committed:

- In pgsql/src/backend/libpq/auth.c, raise the maximum authentication
  token (Kerberos ticket) size in GSSAPI and SSPI athentication
  methods. While the old 2000 byte limit was more than enough for Unix
  Kerberos implementations, tickets issued by Windows Domain
  Controllers can be much larger.  Ian Turner.

- In pgsql/src/backend/libpq/auth.c, rename the new
  MAX_AUTH_TOKEN_LENGTH #define to PG_MAX_AUTH_MAX_TOKEN_LENGTH, to
  make it more obvious that it's a PostgreSQL internal limit, not
  something that comes from system header files.

- In pgsql/src/bin/scripts/vacuumdb.c, FREEZE and VERBOSE options were
  in wrong order in the VACUUM command that vacuumdb produces. Per
  report by Thom Brown.

Michael Meskes committed:

- Made ECPG more robust against applications freeing strings, based on
  patch send in by Zoltan Boszormenyi.

Magnus Hagander committed:

- Write to the Windows eventlog in UTF16, converting the message
  encoding as necessary.  Itagaki Takahiro with some changes from me.

- In pgsql/src/backend/utils/mb/mbutils.c, fix typo in previous
  release as reported by Itagaki Takahiro, but missed by me.

== Abgelehnte Patches (bis jetzt) ==

No one was disappointed this week :-)

== Eingesandte Patches ==

Laurenz Albe sent in another revision of the patch to create a hook to
test password cryptgraphic strength along with a contrib module to use
the hook.

ITAGAKI Takahiro sent in another revision of the patch to fix encoding
issues and eventlog on Win32.

KaiGai Kohei sent in another revision of the patch for large object
ACLs.

Dave Page sent in a WIP patch to add an application_name GUC which
optionally shows the name of the connecting application.

Peter Eisentraut sent in an updated version of the per-column trigger
patch.

KaiGai Kohei sent in another revision of the ACL rework patch.

ITAGAKI Takahiro sent in another revision of the per-column trigger
patch.

Zoltan Boszormenyi sent a patch that makes ECPG more robust against
applications that free() strings by storing its own copy of the
prepared statement name.

ITAGAKI Takahiro sent in a patch to prevent table rewrites caused by
ALTER TABLE from writing WALs.

Heikki Linnakangas sent in an updated patch for Hot Standby.

ITAGAKI Takahiro sent in a patch for contrib/auto_explain which adds
EXPLAIN (ANALYZE|BUFFERS).

ITAGAKI Takahiro sent in a WIP patch to add WHEN to triggers.

Dave Page sent in another revision of the patch to add an
application_name GUC and supporting features for same.

-- 
			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: Tim LandscheidtDate: 2009-10-22 15:09:17
Subject: psql: Keine Ausgabe bei leerem Ergebnis?
Previous:From: Andreas 'ads' ScherbaumDate: 2009-10-12 16:06:01
Subject: == Wöchentlicher PostgreSQL Newsletter - 11. Oktober 2009 ==

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