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

== Wöchentlicher PostgreSQL Newsletter - 24. August 2008 ==

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 - 24. August 2008 ==
Date: 2008-08-25 21:15:49
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-de-allgemein
Der Originalartikel befindet sich unter:

== Wöchentlicher PostgreSQL Newsletter - 24. August 2008 ==

== PostgreSQL Produkt Neuigkeiten ==

Archiveopteryx 2.1.1 und 3.0.0 werden bald erscheinen.

== PostgreSQL Jobs im August ==

== PostgreSQL Lokal ==

Registrierung für PGCon Brasilien 2008 ist offen.

Stefan Kaltenbrunner hält einen Vortrag über Monitoringstrategien für auf der Nagios Konferenz 2008 am 11. und 12. September
in Nürnberg, Deutschland.

Die Prato Linux User Group wird PostgreSQL Vorträge im September
halten. Der Zeitplan in italienisch:

PGCon Brazil 2008 wird vom 26.-27. September auf dem Unicamp in
Campinas stattfinden. wird am 4. Oktober in Toulouse. Der Call for Papers ist
Anmeldung hier:

Der Open Source Tag in Magdeburg findet am 11. Oktober 2008 statt.
Schicke deine interessanten Vorträge für den PostgreSQL Track.
Der Call for Papers ist bis zum 31. August 2008 geöffnet. (in deutsch)

Die PostgreSQL West Konferenz 2008 wird vom 12. bis 12. Oktober in
Portland, State University in Portland, Oregon stattfinden.
Vorträge sind einzureichen unter:

Sponsere den Europäischen PostgreSQL Tag!

Der Call for Papers für den Europäischen PostgreSQL Tag hat begonnen.

PGDay.(IT|EU) 2008 wird am 17. und 18. Oktober in Prato stattfinden.

== PostgreSQL in den News ==

Planet PostgreSQL:

Dieser wöchentliche PostgreSQL Newsletter wurde erstellt von David

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

Magnus Hagander committed:

- In pgsql/src/tools/msvc/clean.bat, properly remove
  src\include\utils\probes.h when running clean.bat.

- In pgsql/src/interfaces/libpq/fe-misc.c, make libpq on windows not
  try to send chunks larger than 64Kb.  Per Microsoft knowledge base
  article Q201213, early versions of Windows fail when we do this.
  Later versions of Windows appear to have a higher limit than 64Kb,
  but do still fail on large sends, so we unconditionally limit it for
  all versions.  Patch from Tom Lane.

Bruce Momjian committed:

- Add to TODO: "Fix all set-returning system functions so they support
  a wildcard target list."

- Mark TODO as done: "Allow an existing index to be marked as a
  table's primary key."

- Not actually done: "Allow an existing index to be marked as a
  table's primary key."

- New TODO list URL wiki location listed; contents truncated.

- TODO now in wiki, html version removed.

- Remove tools and documention for generating TODO.html.

- In pgsql/doc/src/sgml/ref/pg_dump.sgml, mention that pg_dump does
  not dump ALTER DATABASE ... SET commands; backpatch to 8.3.X. Also
  fix markup that had just one bullet.

- Improve wording of error message when a postgresql.conf setting is
  ignored because it can only be set at server start.

- Minor patch on pgbench: 1. -i option should run vacuum analyze only
  on pgbench tables, not *all* tables in database.  2. pre-run cleanup
  step was DELETE FROM HISTORY then VACUUM HISTORY.  This is just a
  slow version of TRUNCATE HISTORY.

- Make "log_temp_files" super-user set only, like other logging
  options.  Simon Riggs.

- Update link to developer's FAQ from main FAQ.

- Add missing descriptions for aggregates, functions and conversions.
  Bernd Helmle.

Alvaro Herrera committed:

- Fix some issues that prevent this file to be processed by scripts.
  While at it, mark a couple of TODO items completed in 8.4: "Prevent
  long-lived temporary tables from causing frozen-xid advancement
  starvation," and "Improve performance of shared invalidation queue
  for multiple CPUs." Also remove a couple of obsolete assignments.

- In pgsql/doc/TODO, update URL.

Magnus Hagander committed:

- In ecpg, fixed incorrect argument handling in SET command if
  argument is a variable.

Tom Lane committed:

- Cause the output from debug_print_parse, debug_print_rewritten, and
  debug_print_plan to appear at LOG message level, not DEBUG1 as
  historically.  Make debug_pretty_print default to on.  Also, cause
  plans generated via EXPLAIN to be subject to debug_print_plan.  This
  is all to make debug_print_plan a reasonably comfortable substitute
  for the former behavior of EXPLAIN VERBOSE.

- Remove -Winline from the default set of CFLAGS for gcc.  It's gotten
  much too noisy to be useful as of gcc 4.3, and we were never really
  doing anything about inlining warnings anyway.

- In pgsql/src/backend/optimizer/plan/subselect.c, fix obsolete
  comment.  It's no longer the case that Param nodes don't carry

- In pgsql/src/backend/optimizer/plan/subselect.c, marginal
  improvement in sublink planning: allow unknownEqFalse optimization
  to be used for SubLinks that are underneath a top-level OR clause.
  Just as at the very top level of WHERE, it's not necessary to be
  accurate about whether the sublink returns FALSE or NULL, because
  either result has the same impact on whether the WHERE will succeed.

- Arrange to convert EXISTS subqueries that are equivalent to hashable
  IN subqueries into the same thing you'd have gotten from IN (except
  always with unknownEqFalse = true, so as to get the proper semantics
  for an EXISTS).  I believe this fixes the last case within CVS HEAD
  in which an EXISTS could give worse performance than an equivalent
  IN subquery.  The tricky part of this is that if the upper query
  probes the EXISTS for only a few rows, the hashing implementation
  can actually be worse than the default, and therefore we need to
  make a cost-based decision about which way to use.  But at the time
  when the planner generates plans for subqueries, it doesn't really
  know how many times the subquery will be executed.  The least
  invasive solution seems to be to generate both plans and postpone
  the choice until execution.  Therefore, in a query that has been
  optimized this way, EXPLAIN will show two subplans for the EXISTS,
  of which only one will actually get executed.  There is a lot more
  that could be done based on this infrastructure: in particular it's
  interesting to consider switching to the hash plan if we start out
  using the non-hashed plan but find a lot more upper rows going by
  than we expected.  I have therefore left some minor inefficiencies
  in place, such as initializing both subplans even though we will
  currently only use one.

Michael Meskes committed:

- In ecpg, synced parser.

- Fixed incorrect argument handling in SET command if argument is a

Peter Eisentraut committed:

- Autoconf 2.62 will require cache variables to contain "_cv_".  Fix
  our few noncomplying cases to be future-proof.

Teodor Sigaev committed:

- Fix possible duplicate tuples while  GiST scan.  Now page is
  processed at once and ItemPointers are collected in memory.  Remove
  tuple's killing by killtuple() if tuple was moved to another page,
  it could produce unaceptable overhead.  Backpatch up to 8.1 because
  the bug was introduced by GiST's concurrency support.

== Abgelehnte Patches (bis jetzt) ==

No one was disappointed this week :-)

== Eingesandte Patches ==

ITAGAKI Takahiro sent in a patch to let people include flags for
custom GUC variables at runtime.

Magnus Hagander sent in a patch to let people change the
stats_temp_directory with a SIGHUP.

D'Arcy J.M. Cain sent in two revisions of a patch to add a new border
setting to psql.

		Andreas 'ads' Scherbaum
Deutsche PostgreSQL User Group:

pgsql-de-allgemein by date

Next:From: Andreas 'ads' ScherbaumDate: 2008-09-01 09:36:08
Subject: == Wöchentlicher PostgreSQL Newsletter - 31. August 2008 ==
Previous:From: Robert MüllerDate: 2008-08-24 19:27:03
Subject: Re: Funktion: Ergebnis kommagetrennt

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