== Postgres Weekly News - 24 agosto 2008 ==

[rotellaro(at)gmail(dot)com]

== PostgreSQL news prodotti ==
Archiveopteryx 2.1.1 e 3.0.0 will verranno rilasciati a breve.
http://aox.org/


== Offerte di lavoro legate a PostgreSQL per il mese di Agosto ==
http://archives.postgresql.org/pgsql-jobs/2008-08/threads.php

== PostgreSQL news locali ==

Sono aperte le registrazioni per il PGCon Brasile 2008.
http://pgcon.postgresql.org.br/inscricoes.en.html

Stefan Kaltenbrunner terrà un talk sulle strategie di monitoraggio per
postgresql.org alla conferenza su Nagios
che si terrà a Norimberga, Germania, i giorni 11 e 12 settembre 2008.
http://www.netways.de/nagios_konferenz/y2008/programm/v/postgresql_monitoring/

Il Prato Linux User Group terrà dei talk su PostgreSQL talks a Settembre.
Il calendario in italiano si trova all'url:
http://www.prato.linux.it/serate_a_tema_2008

Il PGCon Brasile 2008 ci sara' il 26 e 27 settembre 2008 a Unicamp, Campinas.
http://pgcon.postgresql.org.br/index.en.html

Il PgDay.fr ci sarà il 4 ottobrea a Toulouse.  Il Call for Papers è aperto:
http://www.postgresqlfr.org/?q=node/1686
Per registrarsi:
http://www.pgday.fr/doku.php/inscription

L'Open Source Day ci sarà a Magdeburgo, Germania l'11 ottobre 2008.
http://www.open-source-tag.de/
Inviate i vostri talk per il percorso PostgreSQL!
Il call for papers è aperto fino al 31 agosto 2008.
http://www.open-source-tag.de/cfp/index.html (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.
http://www.postgresqlconference.org/
Invio talk all'indirizzo:
http://www.postgresqlconference.org/west08/talk_submission/

Sponsorizzate il PGDay Europeo!
http://www.pgday.org/en/sponsors/campaign

E' iniziato il call for papers per il PGDay europeo.
http://www.pgday.org/en/call4papers

Il PGDay.(IT|EU) 2008 ci sarà il 17 e 18 ottobre a Prato.
http://www.pgday.org/it/

== News su PostgreSQL ==

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

General Bits, archivi e nuovi articoli occasionali:
http://www.varlena.com/GeneralBits/

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:

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

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

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.


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

== Patch in attesa ==

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.

-- 
(all opinions expressed are my own)
Federico Campoli
PostgreSQL Consulting -> PGHost http://www.pghost.eu