Skip to content

Wöchentlicher PostgreSQL Newsletter - 24. Mai 2009

Der Originalartikel befindet sich unter:

== Wöchentlicher PostgreSQL Newsletter - 24. Mai 2009 ==

PostgreSQL 8.4 Beta 2 erschienen. Testen!

PgCon war ein großer Erfolg, mit einer gesteigerten Besucherzahl im
Angesicht von wenigern Besuchern auf anderen Konferenzen. Das Video
zur Konferenz erscheint demnächst.

Das Video vom SFPUG Treffen am 12. Mai 2009, "BIRT & PostgreSQL", ist
jetzt zum Anschauen und Herunterladen auf

Die 10. jährliche JPUG Konferenz hat den Call for Proposals gestartet.

MicroOLAP Database Designer 1.2.8 Beta1, ein Windows-basierender
Designer für PostgreSQL, ist erschienen.

Die PostgreSQL/PostGIS Community wird sich am 6. Juni 2009 in Zürich
treffen. Details (in de_CH) unter:öck

== PostgreSQL Produkt Neuigkeiten ==

== PostgreSQL 8.4 Feature der Woche ==

Warm Standby: Wenn dich das Aufsetzen eines Warm Standby Servers vorher
verwirrt hat, dann gib 8.4 eine Chance; das ist viel

== PostgreSQL Tipp der Woche ==

Bis in 8.4 die Common Table Expressions und in 8.5 das SQL/MED
erscheint, kannst du das "tablefunc" Contrib Modul nutzen, um mittels
connect_by() Joins und Anfragen zwischen verschiedenen Datenbanken
oder der gleichen Datenbank zu nutzen.

== PostgreSQL Jobs im Mai ==

== PostgreSQL Lokal ==

PGDay Junin / Buenos Aires Unnoba wird am 6. Juni 2009 stattfinden.

Termin vormerken: pgDay San Jose, am Sonntag dem 19. Juli unmittelbar
vor der OSCON. CfP und mehr Informationen bald.

PGCon Brasilien wird am 23.-24. Oktober 2009 auf dem Unicamp in
Campinas, Sao Paulo, stattfinden.

PGDay.EU 2009 wird an der Telecom ParisTech Universität in Paris,
Frankreich, am 6. und 7. Nivember 2009 stattfinden.

== PostgreSQL in den News ==

Planet PostgreSQL:

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

Sende Neuigkeiten und Ankündigungen bis Sonntag, 15 Uhr Pazifischer
Zeit. Bitte sende englische Beiträge an, deutsche an, italienische an

== Angewandte Patches ==

Peter Eisentraut committed:

- Some documentation cleanup for the addition of the KOI8U encoding.
  Change all (remaining) mentions of KOI8 to the new canonical form
  KOI8R.  Add information about the available conversions for KOI8U.

- Refer to tables by id, not by "the following table", because tables
  are in theory floating elements.

- In pgsql/src/backend/catalog/sql_features.txt, update SQL
  conformance entries for window functions functionality

- In pgsql/src/tools/editors/emacs.samples, add some instructions on
  how to customize emacs for working on the SGML sources.

- Add documentation string for LDFLAGS_SL in configure --help output.

- In pgsql/src/tools/editors/emacs.samples, fix sgml-mode example.
  Thanks, Andrew Dunstan.

- In pgsql/src/bin/pg_dump/pg_dump.c, convert some messages to use
  ngettext().  Author: Euler Taveira de Oliveira.

Tom Lane committed:

- In pgsql/src/interfaces/libpq/fe-connect.c, make pwdfMatchesString()
  a little more careful about matching * fields.

- Fix bug #4814 (wrong subscript in consistent-function call), and add
  some minimal regression test coverage for matchPartialInPendingList().

- Fix LIKE's special-case code for % followed by _.  I'm not entirely
  sure that this case is worth a special code path, but a special code
  path that gets the boundary condition wrong is definitely no good.
  Per bug #4821 from Andrew Gierth.  In passing, clean up some minor
  code formatting issues (excess parentheses and blank lines in odd
  places).  Back-patch to 8.3, where the bug was introduced.

- Use more-portable coding for the check on handing out the last
  available relopt_kind value in add_reloption_kind().  Per Zdenek

Heikki Linnakangas committed:

- In pgsql/src/backend/commands/analyze.c, update relpages and
  reltuples estimates in stand-alone ANALYZE, even if there's no
  analyzable attributes or indexes. We also used to report 0 live and
  dead tuples for such tables, which messed with autovacuum threshold
  calculations.  This fixes bug #4812 reported by George Su. Backpatch
  back to 8.1.

- In pgsql/src/backend/commands/tablecmds.c, silence a gcc compiler
  warning about non-literal format string with no args when compiling
  with -Wformat-security. Fujii Masao.

Michael Meskes committed:

- Removed some unneeded variables and comparisons.

- More variables gcc moans about.

- Removed unsigned/signed mismatches.

- Removed comparison of unsigned expression < 0.

Teodor Sigaev committed:

- In pgsql/src/backend/utils/adt/tsvector.c, re-sort tsvector's
  lexemes in tsvectorrecv instead of emitting an error.  Basically,
  it's needed to support binary dump from 8.3 because the ordering
  rule was changed.  Per discussion with Bruce Momjian.

== Abgelehnte Patches (bis jetzt) ==

No one was disappointed this week :-)

== Eingesandte Patches ==

Simon Riggs sent in two patches to improve read-only scalability.

Pavel Stehule sent in another revision of the GROUPING SETS patch.

Jim Nasby sent in a patch to add a feature to vacuumdb that allows
analyze-only as an option.

Robert Haas sent in a patch to add parenthesized options to EXPLAIN.

Pavel Stehule sent in a patch to clean up some syntax warnings in

Zdenek Kotala sent in two patches to do some cleanup to help

Tatsuhito Kasahara sent in a patch to fix ja.po.

Steve Prentice sent in two versions of a patch to supplement Pavel
Stehule's patch for named and mixed notation support in 8.5.  Pavel
sent in a followup that touches the main parser.  Steve sent an
updated patch.

Dimitri Fontaine sent in a document patch for GiST extensions.

Adriano Lange sent in a patch implementing 2PO, an alternative to
the GEQO for optimizing large joins.

Andres Freund sent in a patch to allow EXPLAIN ANALYZE to show
counts of discarded tuples.


No Trackbacks


Display comments as Linear | Threaded

No comments

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.
To leave a comment you must approve it via e-mail, which will be sent to your address after submission.
Form options