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

== Postgres Weekly News - 31 agosto 2008 ==

From: rotellaro(at)gmail(dot)com
To: pgsql-it-generale <pgsql-it-generale(at)postgresql(dot)org>
Subject: == Postgres Weekly News - 31 agosto 2008 ==
Date: 2008-09-01 08:30:04
Message-ID: (view raw or flat)
Lists: pgsql-it-generale
La sera del 16 ottobre, il giorno prima del PGDay 2008 sarà
disponibile una developer room.
Facciamone buon uso!

Il 10 settembre è l'ultimo giorno per iscriversi alla partnership
pubblicitaria PGDay 2008 "Borse della conferenza".

Per mantenere la partecipazione al PGDay 2008 gratuita mancano pochi
partner pubblicitari,
in special modo quelli di livello  Argento. Per maggiori informazioni
e anche (ndt.)

Il progetto PostgreSQL RPM Building ha inviato nuovi update delle
versioni 8.3 e 8.2

Victor Vislobokov ha pubblicato un breve riepilogo delle
caratteristiche in russo.

== PostgreSQL news prodotti ==
Rilasciato Benetl 2.3

Rilasciato DBD::Pg 2.10.3

== Offerte di lavoro legate a PostgreSQL per il mese di Agosto ==

== PostgreSQL news locali ==
PostgreSQL avrà un tavolo al LinuxLive, Olympia, Lonkdra, dal 23 al 25
ottobre 2008.  Scrivete a  Dave Page per partecipare.
dpage AT pgamin DOT org

Sono aperte le registrazioni per il PGCon Brasile 2008.

Stefan Kaltenbrunner terrà un talk sulle strategie di monitoraggio per alla conferenza su Nagios
che si terrà a Norimberga, Germania, i giorni 11 e 12 settembre 2008.

Il Prato Linux User Group terrà dei talk su PostgreSQL talks a Settembre.
Il calendario in italiano si trova all'url:

Il PGCon Brasile 2008 ci sara' il 26 e 27 settembre 2008 a Unicamp, Campinas.

Il ci sarà il 4 ottobre a Toulouse.  Il Call for Papers è aperto:
Per registrarsi:

L'Open Source Day ci sarà a Magdeburgo, Germania l'11 ottobre 2008.
Inviate i vostri talk per il percorso PostgreSQL!
Il call for papers è aperto fino al 31 agosto 2008. (in tedesco)

La conferenza su PostgreSQL della costa occidentale per il 2008
ci sarà dal 10 al 12 ottobre alla Portland State University a Portland
stato dell'Oregon.
Invio talk all'indirizzo:

Sponsorizzate il PGDay Europeo!

E' iniziato il call for papers per il PGDay europeo.

Il PGDay.(IT|EU) 2008 ci sarà il 17 e 18 ottobre a Prato.

== News su PostgreSQL ==

Planet PostgreSQL:

General Bits, archivi e nuovi articoli occasionali:

PostgreSQL Weekly News è stato spedito questa settimana grazie a David Fetter.

Per segnalare news e annunci invia un email in inglese entro le ore 15,
fuso orario della costa orientale degli U.S.A, di domenica.

Per segnalazioni in inglese david(at)fetter(dot)org, per segnalazioni in
Tedesco pwn(at)pgug(dot)de, per segnalazioni in italiano pwn(at)itpug(dot)org

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

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

- 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

- 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

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

== Patch rigettate (per ora) ==
Nessuno è stato scontentato questa settimana :-)

== Patch in attesa ==

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

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.

(all opinions expressed are my own)
Federico Campoli
PostgreSQL Consulting -> PGHost

pgsql-it-generale by date

Next:From: Fabio SerraDate: 2008-09-04 08:47:54
Subject: Dump e restore tra due db con diverso encoding
Previous:From: rotellaroDate: 2008-08-29 05:48:22
Subject: == Postgres Weekly News - 24 agosto 2008 ==

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