Skip to content

Wöchentlicher PostgreSQL Newsletter - 19. April 2009

Der Originalartikel befindet sich unter:

== Wöchentlicher PostgreSQL Newsletter - 19. April 2009 ==

PostgreSQL 8.4 Beta 1 erschienen. Testen!

Das "PostgreSQL in the Cloud" Video ist verfügbar. Danke schön an
Christophe Pettus für die Kamera Arbeit und an Dirk Jagdmann für den
Live Stream während der Veranstaltung.

== PostgreSQL Produkt Neuigkeiten ==

Archiveopteryx 3.1.1, ein PostgreSQL-basierter Email Handler,
ist erschienen.

Benetl 2.7, ein ETL Werkzeug für Dateien in PostgreSQL, ist erschienen.

DBD::Pg 2.13.0, ein Perl Connector für PostgreSQL, ist erschienen.

== PostgreSQL 8.4 Feature der Woche ==

FSM Autotuning: hast du die GUC Parameter max_fsm_relations und
max_fsm_pages gemocht? Sehr schade. Sie sind weg, dank Heikki
Linnakangas Arbeit tunen sich die beiden Parameter nun selbst.

== PostgreSQL Tipp der Woche ==

Postgresql unterstützt das INFORMATION_SCHEMA aus dem SQL-Standard,
welches Informationen über Tabellen, Spalten, Constrains und Views
enthält und in der gleichen Weise unter Oracle, DB2 und MySQL zu
finden ist. Zu finden im eingebauten Schema "information_schema".

== PostgreSQL Jobs im April ==

== PostgreSQL Lokal ==

PgDay Florianopolis wird am 22. Mai stattfinden. Kontaktiere Dickson S.
Guedes (guedes AT guedesoft DOT net) um teilzunehmen oder einen Vortrag

Die Percona Performance Konferenz wird im Santa Clara Convention Center
in Santa Clara, Kalifornien, USA, stattfinden.

Der CfP für den PgDay in Sao Paulo am 24. April ist eröffnet.
Kontaktiere marins DOT consultoria AT gmail DOT com oder marcelojscosta
AT gmail DOT com wenn du teilnehmen möchtest.

PostgreSQL Conference U.S. (JDCon) wird einen PgDay auf dem Linuxfest
Nordwest am 25. und 26. April veranstalten. Der Call for Papers ist

Es werden weiterhin PgDays am 29. April in Porto Velho, RO und am 20.
April in Ji-Parana, RO stattfinden. Kontaktiere Luis Fernando Bueno:
proflfbueno AT gmail DOT com wenn du teilnehmen möchtest.

Michael Renner wird einen Workshop über PostgreSQL Replikation auf
der Netways OSDC 2009 in Nürnbern, Deutschland geben.

PGCon 2009 wird vom 21. bis 22. Mai 2009 in Ottawa an der Universität
von Ottawa stattfinden. Dem gehen zwei Tage mit Tutorials vom 19. bis
20. Mai 2009 voraus.

PgDay Florianopolis wird am 22. Mai stattfinden. Kontaktiere Dickson S.
Guedes (guedes AT guedesoft DOT net) um teilzunehmen oder einen Vortrag

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.

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

Tom Lane committed:

- In pgsql/doc/src/sgml/release.sgml, make a copy-editing pass over
  the 8.4 release notes.

- In pgsql/doc/src/sgml/textsearch.sgml, do some copy-editing on
  description of ts_headline().

- In pgsql/src/backend/parser/scan.l, fix broken {xufailed} production
  that made HEAD fail on select u&42 from table-with-a-u-column; Also
  fix missing SET_YYLLOC() in the {dolqfailed} production that I
  suppose this was based on.  The latter is a pre-existing bug, but
  the only effect is to misplace the error cursor by one token, so
  probably not worth backpatching.

- Fix planner to restore its previous level of intelligence about
  pushing constants through full joins, as in SELECT * FROM tenk1 a
  FULL JOIN tenk1 b USING (unique1) WHERE unique1 = 42; which should
  generate a fairly cheap plan where we apply the constraint unique1 =
  42 in each relation scan.  This had been broken by my patch of
  2008-06-27, which is now reverted in favor of a more invasive but
  hopefully less incorrect approach.  That patch was meant to prevent
  incorrect extraction of OR'd indexclauses from OR conditions above
  an outer join.  To do that correctly we need more information than
  the outerjoin_delay flag can provide, so add a nullable_relids field
  to RestrictInfo that records exactly which relations are nulled by
  outer joins that are underneath a particular qual clause.  A side
  benefit is that we can make the test in create_or_index_quals more
  specific: it is now smart enough to extract an OR'd indexclause into
  the outer side of an outer join, even though it must not do so in
  the inner side.  The old coding couldn't distinguish these cases so
  it could not do either.

- In pgsql/src/backend/optimizer/path/costsize.c, bump disable_cost up
  from 1e8 to 1e10, per gripe from Kris Jurka.

- Revise plpgsql's scanner to process comments and string literals in
  a way more nearly matching the core SQL scanner.  The user-visible
  effects are: 1.  Block comments (slash-star comments) now nest, as
  per SQL spec.  2.  In standard_conforming_strings mode, backslash as
  the last character of a non-E string literal is now correctly taken
  as an ordinary character; formerly it was misinterpreted as escaping
  the ending quote.  (Since the string also had to pass through the
  core scanner, this invariably led to syntax errors.)  3.  Formerly,
  backslashes in the format string of RAISE were always treated as
  quoting the next character, regardless of mode.  Now, they are
  ordinary characters with standard_conforming_strings on, while with
  it off, they introduce the same set of escapes as in the core SQL
  scanner.  Also, escape_string_warning is now effective for RAISE
  format strings.  These changes make RAISE format strings work just
  like any other string literal.  This is implemented by copying and
  pasting a lot of logic from the core scanner.  It would be a good
  idea to look into getting rid of plpgsql's scanner entirely in favor
  of using the core scanner.  However, that involves more change than
  I can justify making during beta --- in particular, the core scanner
  would have to become re-entrant.  In passing, remove the kluge that
  made the plpgsql scanner emit T_FUNCTION or T_TRIGGER as a made-up
  first token.  That presumably had some value once upon a time, but
  now it's just useless complication for both the scanner and the

- Fix estimate_num_groups() to not fail on PlaceHolderVars, per report
  from Stefan Kaltenbrunner.  The most reasonable behavior (at least
  for the near term) seems to be to ignore the PlaceHolderVar and
  examine its argument instead.  In support of this, change the API of
  pull_var_clause() to allow callers to request recursion into
  PlaceHolderVars.  Currently estimate_num_groups() is the only
  customer for that behavior, but where there's one there may be

- In pgsql/doc/src/sgml/textsearch.sgml, fix textsearch documentation
  examples to not recommend concatenating separate fields without
  putting a space between.  Per gripe from Rick Schumeyer.

- Fix de-escaping checks so that we will reject \000 as well as other
  invalidly encoded sequences.  Per discussion of a couple of days

- Rethink the idea of having plpgsql depend on parser/gram.h.  Aside
  from the fact that this is breaking the MSVC build, it's probably
  not really a good idea to expand the dependencies of gram.h any
  further than the core parser; for instance the value of SCONST might
  depend on which bison version you'd built with.  Better to expose an
  additional call point in parser.c, so move what I had put into
  pl_funcs.c into parser.c.  Also PGDLLIMPORT'ify the reference to
  standard_conforming_strings, per buildfarm results.

- Assorted portability fixes for Borland C, from Pavel Golub.

Alvaro Herrera committed:

- In pgsql/src/bin/pg_dump/pg_restore.c, make new strings more alike
  previously existing messages.

- In pgsql/src/bin/pg_dump/pg_restore.c, pg_restore -jN does not
  equate "multiple jobs", so partly revert the previous patch.  Per
  note from Tom Lane.

- In pgsql/src/backend/commands/dbcommands.c, add missing periods.

- In pgsql/src/backend/libpq/hba.c, add missing gettext calls around
  some strings.  Also remove quotes around the %s that they expand to,
  per comment from Tom Lane.

- In pgsql/src/backend/utils/adt/arrayfuncs.c, substitute extraneous
  underscores with spaces.

- In pgsql/src/test/regress/expected/arrays.out, fix the regression
  test error message for array_fill, too.  Per note from Andrew

Bruce Momjian committed:

- In pgsql/src/interfaces/libpq/fe-secure.c, add libpq error message
  text on how to handle missing root.crt file.

- In pgsql/doc/src/sgml/libpq.sgml, reformat 'sslmode' options into an
  SGML table;  improve wording.

- In pgsql/doc/src/sgml/libpq.sgml, fix SGML markup I broke yesterday.

- Remove mention of pre-7.1 inheritance behavior from /ref pages; keep
  mentions in main documentation.

- In pgsql/doc/src/sgml/release.sgml, add Ron Mayer as primary
  contributor for, "support the IS0 8601 interval syntax" based on
  private email from Ron.

Magnus Hagander committed:

- In pgsql/contrib/pgcrypto/crypt-md5.c, remove beer-ware license from
  crypt-md5.c, per approval from Poul-Henning Kamp.  This makes the
  file the same standard 2-clause BSD as the rest of PostgreSQL.

== Abgelehnte Patches (bis jetzt) ==

KaiGai Kohei's patch to separate the ACL for SELECT ... FOR UPDATE
from UPDATE.  Not needed.

== Eingesandte Patches ==

Abhijit Menon-Sen sent in another revision of his patch to test
quoting in PL/pgSQL.

ITAGAKI Takahiro sent in a patch to implement GetPlatformEncoding()
and convert absolute file paths from database encoding to platform

David Fetter sent in three patches to make \df describe whether a
function is normal, aggregate, trigger or windowing and let people
choose any or all of those to see.

ITAGAKI Takahiro sent in a WIP patch to solve server-side encoding

Fujii Masao sent in another revision of his trigger patch for

Marko Kreen sent in a patch to add \u and \U as unicode escapes.

KaiGai Kohei sent in another revision of his SE-PostgreSQL patches.


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