(Traduzione parziale in lingua italiana delle PostgreSQL Weekly News a cura di Gianni Ciolli gianni.ciolli@2ndquadrant.it)
La comunità PostgreSQL in lingua spagnola ha adesso il suo sito web. Complimenti! http://www.postgresql-es.org/
Rilasciata la versione 2.13.1 di DBD::Pg, un connettore Perl per PostgreSQL. http://search.cpan.org/dist/DBD-Pg/
Rilasciata la versione 1.1 di pgFouine, un programma per analizzare i log e generare report. http://pgfouine.projects.postgresql.org/
Rilasciata la versione 2.2.1 di pgpool-II, un connection pooler (e non solo). http://pgfoundry.org/projects/pgpool/
Rilasciata la versione 1.0 di Slony-ctl, un insieme di script per creare e gestire dei cluster Slony. http://pgfoundry.org/projects/slony1-ctl/
pg_
stat_
functions: questa nuova vista di sistema mostra quante volte una determinata funzione è stata eseguita, e quanto tempo ha consumato durante l’esecuzione.
PostgreSQL supporta i sotto-select nelle clausole SELECT, FROM e WHERE. Di conseguenza, rifletti su dove collocare il sotto-select, in modo da migliorare le prestazioni e ottenere i risultati voluti.
http://archives.postgresql.org/pgsql-jobs/2009-04/threads.php
Il PgDay di Florianopolis (Brasile) sarà il 22 maggio. Mettetevi in contatto con Dickson S. Guedes (guedes AT guedesoft DOT net) per partecipare o inviare un lavoro. http://www.postgresql.org.br/eventos/pgday/sc
La Percona Performance Conference si svolgerà presso il Santa Clara Convention Center, Santa Clara, California, USA http://conferences.percona.com/
Aperto il CfP per il PgDay São Paulo, che si terrà il 24 aprile. Per partecipare mettersi in contatto con marins DOT consultoria AT gmail DOT com oppure marcelojscosta AT gmail DOT com.
La PostgreSQL Conference U. S. (JDCon) organizzerà un PgDay nell’ambito della LinuxFest Northwest (25, 26 aprile). Informazioni su come proporre una comunicazione sono disponibili sul sito http://www.postgresqlconference.org/
Ci saranno anche dei PgDay il 29 aprile a Porto Velho, RO, e il 30 in Ji-Parana, RO. Per partecipare mettersi in contatto con Luis Fernando Bueno: proflfbueno AT gmail DOT com.
Michael Renner farà un workshop sulla replica con PostgreSQL a Netways OSDC 2009 il 29 e 30 aprile a Norimberga, in Germania. http://www.netways.de/english/osdc/y2009/programm/w/michael_
renner_
postgresql_
repliziert_
ein_
ueberblick/
Nei giorni 21 e 22 maggio 2009 all’università di Ottawa, in Canada, si terrà PGCon 2009. Nei due giorni precedenti si terranno dei tutorials. http://www.pgcon.org/2009/
Segnatevi la data: pgDay San Jose (USA). Domenica 19 luglio subito prima di OSCON. Saranno presto annunciate ulteriori informazioni! (incluso il call for papers)
Il 23 e 24 ottobre 2009 si svolgerà PGCon Brazil, presso Unicamp, nella città di Campinas, stato di San Paolo.
Planet PostgreSQL: http://planet.postgresql.org/
Questo notiziario settimanale PostgreSQL è stato realizzato da David Fetter e Josh Berkus; traduzione parziale in lingua italiana a cura di Gianni Ciolli.
Notizie o annunci destinati a questo notiziario dovranno pervenire entro la mezzanotte di domenica (le 15 nel fuso orario della California). I comunicati in lingua italiana dovranno essere inviati a pwn@itpug.org; per le lingue inglese o tedesca, si scriva rispettivamente a david@fetter.org o a pwd@pgug.de.
Magnus Hagander committed:
In pgsql/src/tools/msvc/Install.pm, read nls.nk files to determine the proper name of NLS catalogs to install. Hiroshi Inoue, with minor modifications by me.
Move gettext encoding names into encnames.c, so we only have one place to update. Per discussion.
Remove sslverify parameter again, replacing it with two new sslmode values: "verify-ca" and "verify-full". Since "prefer" remains the default, this will make certificate validation off by default, which should lead to less upgrade issues.
In pgsql/doc/src/sgml/release.sgml, remove sslverify parameter from release notes, mention that sslmode is used instead.
In pgsql/doc/src/sgml/libpq.sgml, more clearly document what the different sslmode options mean, both the new and the old ones. Consistently talk about certificate verification, and not validation.
Bruce Momjian committed:
Add agg/normal/trigger/window flags for psql df and in df output. David Fetter.
Merge psql df options into a single ? line, and update docs.
Improve psql df error handling. David Fetter.
In pgsql/src/bin/psql/help.c, use brackets in psql df ? help.
In pgsql/doc/src/sgml/runtime.sgml, improve server spoofing wording, per request from Magnus Hagander.
Remove HELIOS Software GmbH name and copyright from AIX dynloader files, per approval from Helmut Tschemernjak, President. Only back branches; files removed from CVS HEAD.
Tom Lane committed:
In pgsql/src/backend/port/dynloader/osf.c, fix obsolete cross-reference (this file isn’t called alpha.c anymore)
Remove the long-obsolete homebrew dl() functions for AIX, in favor of just using the system functions all the time. (These files are now just copies of the osf. files.) The homebrew functions were not getting used anyway on AIX versions that have dlopen(), that is 4.3 and up, so they are not needed on any AIX that is even remotely supported by the vendor anymore. We’d have probably left them here anyway, except some questions were raised about the copyright.
Change the default value of max_
prepared_
transactions to zero, and add documentation warnings against setting it nonzero unless active use of prepared transactions is intended and a suitable transaction manager has been installed. This should help to prevent the type of scenario we’ve seen several times now where a prepared transaction is forgotten and eventually causes severe maintenance problems (or even anti-wraparound shutdown). The only real reason we had the default be nonzero in the first place was to support regression testing of the feature. To still be able to do that, tweak pg_
regress to force a nonzero value during "make check". Since we cannot force a nonzero value in "make installcheck", add a variant regression test "expected" file that shows the results that will be obtained when max_
prepared_
transactions is zero. Also, extend the HINT messages for transaction wraparound warnings to mention the possibility that old prepared transactions are causing the problem. All per today’s discussion.
In pgsql/src/backend/commands/dbcommands.c, don’t use the result of strcmp as if it were a boolean. A service of your local coding style police.
In pgsql/src/backend/libpq/ip.c, suppress some ‘variable may be used uninitialized’ warnings from gcc 4.4.
In pgsql/src/backend/parser/parse_
func.c, fix some more ‘variable may be used uninitialized’ warnings from gcc 4.4.
Fix the handling of sub-SELECTs appearing in the arguments of an outer-level aggregate function. By definition, such a sub-SELECT cannot reference any variables of query levels between itself and the aggregate’s semantic level (else the aggregate would’ve been assigned to that lower level instead). So the correct, most efficient implementation is to treat the sub-SELECT as being a sub-select of that outer query level, not the level the aggregate syntactically appears in. Not doing so also confuses the heck out of our parameter-passing logic, as illustrated in bug report from Daniel Grace. Fortunately, we were already copying the whole Aggref expression up to the outer query level, so all that’s needed is to delay SS_
process_
sublinks processing of the sub-SELECT until control returns to the outer level. This has been broken since we introduced spec-compliant treatment of outer aggregates in 7.4; so patch all the way back.
Update citext expected output to exactly match the real output, rather than having some whitespace discrepancy. Although whitespace is supposed to be ignored in our regression tests, for some reason buildfarm member spoonbill doesn’t like it.
In pgsql/src/bin/psql/copy.c, remove Windows-specific definition of S_
ISDIR(). This should not be here; if there are any Windows configurations where port/win32.h fails to provide the macro, it should be fixed in the latter file not here.
In pgsql/doc/src/sgml/release.sgml, some more work on the 8.4 release notes. Document a few changes that Bruce apparently found uninteresting, and do minor wordsmithing on a number of the existing entries.
Heikki Linnakangas committed:
In pgsql/src/backend/access/transam/xlog.c, after archive recovery, mark the last WAL segment from the parent timeline ready for archival. It was marked at the next checkpoint anyway, but waiting for the next checkpoint is an unnecessary delay. Fujii Masao.
varstr_
cmp and any comparison function that piggybacks on it can return any negative or positive number, not just -1 or 1. Fix comment on varstr_
cmp and citext test case accordingly. As pointed out by Zdenek Kotala, and buildfarm member gothic moth.
In pgsql/doc/src/sgml/maintenance.sgml, improve the documentation on 8.4 visibility map related VACUUM changes. Explain how vacuum_
freeze_
table_
age should be tuned, and how it relates to the other settings. Mention that vacuum_
freeze_
table_
age also affects when autovacuum scans the whole table.
In pgsql/doc/src/sgml/storage.sgml, mention that tables have a visibility map fork alongside the main fork and FSM.
No one was disappointed this week :-)
Pavel Stehule sent in another revision of his patch to add transformation hooks into the parser.
Fujii Masao sent in two more revisions of the stats_
temp_
directory patch.
Hiroshi Inoue sent in a patch which adds some encoding conversion logic on Windows.
Fujii Masao sent in another revision of the pg_
standby trigger patch.
Tom Lane sent in a patch to fix a performance regression in hash joins.
Robert Haas sent in an experimental patch to change NTUP_
PER_
BUCKET into a GUC called hash_
load, and add EXPLAIN support to show the number of buckets and batches.
Brendan Jurd sent in an updated version of Pavel Stehule’s patch to add scientific notation to to_
char().
Hannu Valtonen sent in a patch to add support for integer and text arrays to PL/PythonU.
This Post Has 0 Comments