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

== Postgres Weekly News - 20 gennaio 2008 ==

From: rotellaro(at)gmail(dot)com
To: itpug-soci(at)lists(dot)itpug(dot)org, pgsql-it-generale <pgsql-it-generale(at)postgresql(dot)org>
Subject: == Postgres Weekly News - 20 gennaio 2008 ==
Date: 2008-01-21 21:38:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-it-generale
Traduzione italiana di PostgreSQL Weekly News by Rotellaro.

Per errori di traduzione o omissioni scrivere a rotellaro (at)

Italian translation of PWN by Rotellaro.

You can find the original post here

PostgreSQL ha vinto il premio come Prodotto dell'anno 2008 su

IT-PUG ha firmato una lettera aperta al ministro italiano

== Postgres News prodotti ==
Rilasciato DBD::Pg 2.0.0_5 (RC5) .

Rilasciato PGCluster-1.5.0rc17 .

Rilasciato pg_proboscis 0.9.3 .

IT-PUG ha creato un plugin Firefox per aggiungere la ricerca nella 
documentazione di PostgreSQL.

Rilasciato Visual SQL Builder Pre-Alpha 0.3 . Contributor e tester sono 
piu' che graditi.

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

== PostgreSQL news locali ==

Il primo meeting del NYPUG avvera' presso lo Skylight Diner January 22 7:30pm
Date conferma di partecipazione all'email josh <AT>

L'European PostgreSQL User Group eleggera' il consiglio direttivo.
Per suggerire le candidature e per informazioni sulle modalita' di voto 

Le novita' di PostgreSQL 8.3 - Colazione con Bruce Momjian
24 Gennaio 2008 - Londra.  Scrivete a questa email per partecipare:
info.emea <AT>

Il PostgreSQL Developers' Day 2008 di Praga avra' luogo il 13 febbraio.

Il PGCon 2008 ci sara' dal 20 al 23 a Ottawa - si accettano proposte di 

I team BSD e PostgreSQL condivideranno una developer room al FOSDEM 2008 
a Bruxelles dal 23 al 24 febbraio 2008. Per proporre talk o per offrire 
il proprio aiuto nella gestione della dev room contattare 
fosdem(at)pgug(dot)eu(dot)  Per maggiori informazioni visitare:

La conferenza della costa orientale di PostgreSQL '08 ci sara' il 29 e 
il 30 marzo al College Park dell'Universita' del Maryland. Il Call for 
Papers e' aperto.

Il FISL 9.0 ci sara' dal 17 al 19 aprile 2008 al PUCRS a Porto Alegre, 

== News su PostgreSQL ==

Planet PostgreSQL:

General Bits, archivi e nuovi articoli occasionali:

PostgreSQL Weekly News รจ stato spedito questa settimana grazie a David 
Fetter e Robert Treat.

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 ==
Michael Meskes committed:

- In ecpg, set valid return values even in case of an error to prevent

- In ecpg, re-enabled variables in fetch/move command.

Alvaro Herrera committed:

- In pgsql/src/backend/postmaster/autovacuum.c, mark autovacuum
  entries in pg_stat_activity so that they can be easily distinguished
  from user-invoked commands.  Per suggestion from Tom Lane.

- In pgsql/src/backend/postmaster/autovacuum.c, backpatch my fix of
  rev 1.48 to avoid a division-by-zero error in the cost-limit vacuum
  code.  Per trouble report from Joshua Drake.

Tom Lane committed:

- Fix an ancient oversight in libpq's handling of V3-protocol COPY OUT
  mode: we need to be able to swallow NOTICE messages, and potentially
  also ParameterStatus messages (although the latter would be a bit
  weird), without exiting COPY OUT state.  Fix it, and adjust the
  protocol documentation to emphasize the need for this.  Per off-list
  report from Alexander Galler.

- In pgsql/src/backend/utils/misc/guc.c, avoid cluttering the
  postmaster log with bogus complaints during transaction abort, per
  my note from a couple days ago.

- In pgsql/src/bin/pg_dump/pg_backup_archiver.c, prevent pg_dump from
  dumping the comment (if any) on the 'public' schema.  This is to
  avoid uselessly requiring superuser permissions to restore the dump
  without errors.  Pretty grotty, but no better alternative seems
  available, at least not in the near term.

- In pgsql/doc/src/sgml/errcodes.sgml, somebody forgot to add the "NOT
  AN XML DOCUMENT" ERRCODE everywhere it should go ...

- In pgsql/src/backend/tsearch/wparser.c, tweak new error message to
  conform to style guidelines.

- Revise memory management for libxml calls.  Instead of keeping
  libxml's data in whichever context happens to be current during a
  call of an xml.c function, use a dedicated context that will not go
  away until we explicitly delete it (which we do at transaction end
  or subtransaction abort).  This makes recovery after an error much
  simpler --- we don't have to individually delete the data structures
  created by libxml.  Also, we need to initialize and cleanup libxml
  only once per transaction (if there's no error) instead of once per
  function call, so it should be a bit faster.  We'll need to keep an
  eye out for intra-transaction memory leaks, though.  Alvaro and Tom.

- In pgsql/src/backend/commands/cluster.c, prevent CLUSTER from
  decreasing a relation's relfrozenxid.  Bug introduced in rewrite to
  make CLUSTER MVCC-safe.

- Be less wishy-washy in the documentation and comments about whether
  a ParameterStatus message can be sent during COPY OUT: it's
  definitely possible, since COPY from a SELECT subquery can trigger
  any user-defined function.

- In pgsql/contrib/start-scripts/osx/PostgreSQL, remove inappropriate
  cd commands, per David Wheeler.  Also make the PATH responsive to
  the installation prefix, which was the apparent intent of the
  previous edit, but not well executed.

- Fix ALTER INDEX RENAME so that if the index belongs to a unique or
  primary key constraint, the constraint is renamed as well.  This
  avoids inconsistent situations that could confuse pg_dump (not to
  mention humans).  We might at some point provide ALTER TABLE RENAME
  CONSTRAINT as a more general solution, but there seems no reason not
  to allow doing it this way too.  Per bug #3854 and related

- Fix pgsql/src/backend/optimizer/plan/subselect.c to avoid assuming
  that a SubLink's testexpr references each subquery output column
  exactly once left-to-right.  Although this is the case in the
  original parser output, it might not be so after rewriting and
  constant-folding, as illustrated by bug #3882 from Jan Mate.
  Instead scan the subquery's target list to obtain needed per-column
  information; this is duplicative of what the parser did, but only a
  couple dozen lines need be copied, and we can clean up a couple of
  notational uglinesses.  Bug was introduced in 8.2 as part of
  revision of SubLink representation.

- Insert into getCopyDataMessage() the same logic that already existed
  in the main code path for enlarging libpq's input buffer in one
  swoop when needing to read a long data message.  Without this, the
  code will double the buffer size, read more data, notice it still
  hasn't got the whole message, and repeat till it finally has a large
  enough buffer.  Which wastes a lot of data-moving effort and also
  memory (since malloc probably can't do anything very useful with the
  freed-up smaller buffers).  Not sure why this wasn't there already;
  certainly the COPY data path is a place where we're quite likely to
  see long data messages.  I'm not backpatching though, since this is
  just a marginal performance issue rather than a real bug.

- In pgsql/src/test/regress/pg_regress.c, make pg_regress clean out
  the testtablespace directory only on Windows.  On other platforms
  it's better to let the Makefile handle it, but we want the
  regression tests to be invokable without make on Windows.  A batch
  file would be a better solution, but no time for that before 8.3.
  Per my discovery that this breaks testing under SELinux, and
  subsequent discussion.

Bruce Momjian committed:

- Add to TODO: "Add the ability to automatically create materialized
  views.  Right now materialized views require the user to create
  triggers on the main table to keep the summary table current.  SQL
  syntax should be able to manager the triggers and summary table
  automatically.  A more sophisticated implementation would
  automatically retrieve from the summary table when the main table is
  referenced, if possible."

- In FAQ, most recent Postgres version is 8.2.6, per report from
  Robert Treat.

- Improve usage message for pgindent.

- Update Japanese FAQ.  Jun Kuwamura.

- Stamp release for 8.3RC2;  configure will be stamped by packager.

Teodor Sigaev committed:

- In pgsql/src/backend/tsearch/wparser.c, add check of headline method
  presence.  Per report by Yoshiyuki Asaba.

- In pgsql/src/backend/tsearch/spell.c, fix core dump with
  buffer-overrun from too-long infinitive.  Add checking of using
  fixed length arrays to prevent array's overrun.  Per report by
  Hannes Dorbath and comments by Tom Lane.

Andrew Dunstan committed:

- Document the fact that COPY always uses the client encoding.

Magnus Hagander committed:

- In pgsql/doc/src/sgml/pgcrypto.sgml, typo fix per Erik Rijkers.

- Marko Kreen's updates to pgsql/doc/src/sgml/pgcrypto.sgml which
  touch on SHA1, SHA224, SHA256, SHA384 and SHA512 encryption and
  change references to RFC 2440 to RFC 4880.

Marc Fournier committed:

- must commit after autoconf ... and yes, I used the right autoconf

== Patch rigettate (per ora) ==

Nessuno e' stato scontentato questa settimana :-)

== Patch in attesa ==
Tom Lane sent in a revision of Alvaro Herrera's XML memory allocation

Federico Campoli is:
@ ITPUG -> Segretario,
@ PLUG -> Presidente,
PostgreSQL Consulting  -> PGHost
(any opinions expressed are my own)

pgsql-it-generale by date

Next:From: rotellaroDate: 2008-01-23 11:34:38
Subject: E' disponibile la Release candidate 2 di PostgreSQL 8.3
Previous:From: rotellaroDate: 2008-01-18 09:17:11
Subject: Re: [itpug] PostgreSQL votato miglior database dell'anno

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