Skip to content

Wöchentlicher PostgreSQL Newsletter - 31. August 2008


Der Originalartikel befindet sich unter:
http://people.planetpostgresql.org/dfetter/


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

Das September Commitfest startet morgen.

Ein PostgreSQL Developber Room ist am Abend des 16. Oktober, dem Tag
vor PGDay 2008 verfügbar. Nutzt dieses Angebot gut aus!

Der 10. September ist der letztmögliche Tag um sich als Sponsor für
die Konferenztaschen auf dem PGDay 2008 zu bewerben.

Für einen PGDay 2008 mit freiem Eintritt benötigen wir ein paar
weitere Sponsoren, speziell vom Silver-Level aufwärts. Bitte besuche
die Partnerschafts-Seite für mehr Informationen:
http://www.pgday.org/en/sponsors/campaign

Das PostgreSQL RPM Buildung Projekt hat neue Updates für 8.3 und
8.2 erstellt.
http://yum.pgsqlrpms.org

Victor Vislobokov hat auf Russisch einen kurzen Feature Überblick
erstellt.
http://postgresql.ru.net/docs/overview.html

== PostgreSQL Produkt Neuigkeiten ==

Benetl 2.3 erschienen.
http://www.benetl.net

DBD::Pg 2.10.3 erschienen.
http://search.cpan.org/dist/DBD-Pg/

== PostgreSQL Jobs im August ==

http://archives.postgresql.org/pgsql-jobs/2008-08/threads.php

== PostgreSQL Lokal ==

PostgreSQL hat einen Stand auf der LinuxLive, Olymbia, in Londok (GB)
vom 23-25. Oktober 2008. Schreibe Dave Page wenn du teilnehmen möchtest.
dpage AT pgamin DOT org

Registrierung für PGCon Brasilien 2008 ist möglich.
http://pgcon.postgresql.org.br/inscricoes.en.html

Stefan Kaltenbrunner hält einen Vortrag über Monitoringstrategien für
postgresql.org auf der Nagios Konferenz 2008 am 11. und 12. September
in Nürnberg, Deutschland.
http://www.netways.de/nagios_konferenz/y2008/programm/v/postgresql_monitoring/

Die Prato Linux User Group wird PostgreSQL Vorträge im September
halten. Der Zeitplan in italienisch:
http://www.prato.linux.it/serate_a_tema_2008

PGCon Brazil 2008 wird vom 26.-27. September auf dem Unicamp in
Campinas stattfinden.
http://pgcon.postgresql.org.br/index.en.html

PgDay.fr wird am 4. Oktober in Toulouse. Der Call for Papers ist
eröffnet:
http://www.postgresqlfr.org/?q=node/1686
Anmeldung hier:
http://www.pgday.fr/doku.php/inscription

Der Open Source Tag in Magdeburg findet am 11. Oktober 2008 statt.
http://www.open-source-tag.de/
Schicke deine interessanten Vorträge für den PostgreSQL Track.
Der Call for Papers ist bis zum 31. August 2008 geöffnet.
http://www.open-source-tag.de/cfp/index.html (in deutsch)

Die PostgreSQL West Konferenz 2008 wird vom 12. bis 12. Oktober in
Portland, State University in Portland, Oregon stattfinden.
http://www.postgresqlconference.org/
Vorträge sind einzureichen unter:
http://www.postgresqlconference.org/west08/talk_submission/

PGDay.(IT|EU) 2008 wird am 17. und 18. Oktober in Prato stattfinden.
Die Registrierung ist bald möglich.
http://www.pgday.org/en/

== PostgreSQL in den News ==

Planet PostgreSQL: http://www.planetpostgresql.org/

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

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

== Angewandte Patches ==

Magnus Hagander committed:

- Convert remaining builtin set-returning functions to use OUT
parameters, making it possible to call them without specifying a
column list. Jaime Casanova.

- Make stats_temp_directory PGC_SIGHUP, and document how it may cause
a temporary "outage" of the statistics views. This requires making
the stats collector respond to SIGHUP, like the other utility
processes already did.

- Unconditionally write the statsfile when SIGHUP is received, to
minimize the window during which backends have no statistics file to
read.

Alvaro Herrera committed:

- In pgsql/doc/src/sgml/Makefile, have man page generation work on
VPATH builds too.

- In pgsql/src/backend/utils/hash/pg_crc.c, update URL to Ross
William's paper. Devrim GUNDUZ.

- In pgsql/src/bin/psql/help.c, document that \t and \x are now
settable.

- Fixup pg_dumpall adding --lock-wait-timeout, to match pg_dump.
David Gould.

Tom Lane committed:

- In pgsql/doc/src/sgml/config.sgml, add standard boilerplate sentence
about when stats_temp_directory can be changed.

- Get rid of the last remaining uses of var_is_rel(), to wit some
debugging checks in ExecIndexBuildScanKeys() that were inadequate
anyway: it's better to verify the correct varno on an expected index
key, not just reject OUTER and INNER. This makes the entire current
contents of nodeFuncs.c dead code. I'll be replacing it with some
other stuff later, as per recent proposal.

- Move exprType(), exprTypmod(), expression_tree_walker(), and related
routines into nodes/nodeFuncs, so as to reduce wanton
cross-subsystem #includes inside the backend. There's probably more
that should be done along this line, but this is a start anyway.

- Add %option noinput to contrib's flex scanners, to suppress gcc 4.3
warnings. Peter did this for core awhile ago but evidently missed
contrib.

- In pgsql/doc/src/sgml/ref/pg_dump.sgml, fix pg_dump docs to
acknowledge that you can use -Z with plain text output. Pointed out
by Daniel Migowski.

- In pgsql/src/backend/optimizer/util/clauses.c, teach
eval_const_expressions() to simplify an ArrayCoerceExpr to a
constant when its input is constant and the element coercion
function is immutable (or nonexistent, ie, binary-coercible case).
This is an oversight in the 8.3 implementation of ArrayCoerceExpr,
and its result is that certain cases involving IN or NOT IN with
constants don't get optimized as they should be. Per
experimentation with an example from Ow Mun Heng.

- Extend the parser location infrastructure to include a location
field in most node types used in expression trees (both before and
after parse analysis). This allows us to place an error cursor in
many situations where we formerly could not, because the information
wasn't available beyond the very first level of parse analysis.
There's a fair amount of work still to be done to persuade
individual ereport() calls to actually include an error location,
but this gets the initdb-forcing part of the work out of the way;
and the situation is already markedly better than before for
complaints about unimplementable implicit casts, such as CASE and
UNION constructs with incompatible alternative data types. Per my
proposal of a few days ago.

- In
pgsql/src/backend/utils/mb/conversion_procs/euc_jis_2004_and_shift_jis_2004/euc_jis_2004_and_shift_jis_2004.c,
suppress gcc warning about possibly-uninitialized variable. It's not
clear to me why I'd not seen this message before --- on F-9 it seems to
only happen if Asserts are disabled, which ought to be irrelevant.
Maybe that affects a decision whether to inline get_ten(), which would
be needed to expose the warning condition to the compiler? Anyway, the
fix is clear.

- In pgsql/src/backend/parser/parse_expr.c, fix bug in original
implementation of xmlserialize(): if user specifies a target type
that isn't acceptable, the code failed to raise the proper error.
The result instead was to return a NULL expression tree, which in a
quick test led to a 'cache lookup failed for type 0' error later.
Patch 8.3 only --- I fixed this in HEAD as part of recent locations
patch.

- In GCC-based builds, use a better newNode() macro that relies on
GCC-specific syntax to avoid a useless store into a global variable.
Per experimentation, this works better than my original thought of
trying to push the code into an out-of-line subroutine.

- Fix the raw-parsetree representation of star (as in SELECT * FROM or
SELECT foo.*) so that it cannot be confused with a quoted identifier
"*". Instead create a separate node type A_Star to represent this
notation. Per pgsql-hackers discussion of 2007-Sep-27.

- Fix (hopefully) some oversights in recent Bison cleanup patch. Per
buildfarm results.

Peter Eisentraut committed:

- Remove all traces that suggest that a non-Bison yacc might be
supported, and change build system to use only Bison. Simplify
build rules, make file names uniform. Don't build the token table
header file where it is not needed.

== Abgelehnte Patches (bis jetzt) ==

No one was disappointed this week :-)

== Eingesandte Patches ==

Laszlo Benedek sent in two revisions of a patch to let people set a
role to a user before dumping the database.

ITAGAKI Takahiro sent in an auto-explain patch.

Michelle Caisse sent in a patch to generate code coverage statistics.

Martin Pihlak sent in another revision of his plan invalidation patch
for stored procedures.

ITAGAKI Takahiro sent in a contrib version of his auto-explain patch.

Alvaro Herrera sent in a patch to add source file and line numbers to
GUC variables in the pg_settings view.

Heikki Linnakangas sent in another revision of his FSM patch.

Hitoshi Harada sent in another revision of his patch implementing
windowing functions.

Karl Schnaitter sent in a patch intended to fix a but in
backend/utils/time/combocid.c, changing the assumption that the raw
command id corresponds to cmin to allow for the case when it may be a
combo id.

Brendan Jurd sent in a patch to improve error handling in to_date()
and to_timestamp() per previous discussions.

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

Simon Riggs sent in a patch to add resource manager hooks along with a
contrib module that uses same.

Simon Riggs sent in a WIP patch to remove JOINs under some
circumstances.

Simon Riggs sent in a patch to change the recovery infrastructure
which decouples the death of the startup process to the change of
state in the postmaster following recovery.

Ryan Bradetich sent in a pair of patches implementing unsigned integer
types and doing regression tests on same.

Radek Strnad sent in a WIP patch for collation support.

Zdenek Kotala sent in a prototype of his in-place upgrade patch.

David Rowley sent in two revisions of a patch intended to implement
Boyer-Moore string searching.

Marko Kreen sent in a patch to make gram.y use palloc and pfree for
memory management.

Marko Kreen sent in a patch intended to change from case-sensitive
units ("kB" vs. "KB") in GUC variables to case-insensitive ones, and
to clean up the way GUCs are handled on INT64_IS_BUSTED platforms.

Marko Kreen sent in a patch to clarify the error for mismatched magic
blocks in the module and server for SPI.

Gregory Stark sent in a patch to improve CLUSTER performance by having
it use a sort.
  • Twitter
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 31. August 2008 at del.icio.us
  • Facebook
  • Google Bookmarks
  • FriendFeed
  • Digg Wöchentlicher PostgreSQL Newsletter - 31. August 2008
  • Bloglines Wöchentlicher PostgreSQL Newsletter - 31. August 2008
  • Technorati Wöchentlicher PostgreSQL Newsletter - 31. August 2008
  • Fark this: Wöchentlicher PostgreSQL Newsletter - 31. August 2008
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 31. August 2008 at YahooMyWeb
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 31. August 2008 at Furl.net
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 31. August 2008 at reddit.com
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 31. August 2008 at blinklist.com
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 31. August 2008 at Spurl.net
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 31. August 2008 at Simpy.com
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 31. August 2008 at blogmarks
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 31. August 2008 with wists
  • wong it!
  • Bookmark using any bookmark manager!
  • Stumble It!
  • Identi.ca

Trackbacks

No Trackbacks

Comments

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