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

== Postgres Weekly News - 13 aprile 2008 ==

From: rotellaro(at)gmail(dot)com
To: pgsql-it-generale <pgsql-it-generale(at)postgresql(dot)org>, itpug(at)lists(dot)itpug(dot)org, itpug-soci(at)lists(dot)itpug(dot)org
Subject: == Postgres Weekly News - 13 aprile 2008 ==
Date: 2008-04-14 07:07:58
Message-ID: a3e8e2210804140007h28d44adfj59722bec1c2c7db1@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-it-generale
== Postgres News prodotti ==
rilasciato check_postgres 1.4.2.
http://bucardo.org/nagios/

Rilasciato Npgsql 2 Beta3.
http://pgfoundry.org/projects/npgsql/

Rilasciato pg_bulkload-2.3.0.
http://pgbulkload.projects.postgresql.org/

Rilasciato pgpool-II 2.1 beta2.
http://pgfoundry.org/projects/pgpool/

Rilasciato pg_top 3.6.2-beta3 released, pg_top era precedentemente
conosciuto come ptop.
http://ptop.projects.postgresql.org/

Rilasciati gli SkyTools 2.1.6.
http://pgfoundry.org/projects/skytools/

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

== PostgreSQL news locali ==
La conferenza Russian Internet Technologies 2008 ci sarà il 14 e 15
aprile a Mosca.
http://rit2008.ru

ITPUG presenterà il talk "PostgreSQL, un database libero per la
Pubblica Amministrazione Italiana" a Pula, Sardegna, al PAAL 2008,
l'evento principale per il free software nella pubblica
amministrazione italiana.
http://www.paal2008.it/

Il FISL 9.0 ci sarà dal 17 al 19 aprile presso il PUCRS a Porto Alegre, Brasile.
https://fisl.softwarelivre.org/9.0/

L'Unicamp PostgreSQL Day  2008 ci sara' il 22 aprile a Campinas, SP, Brasile.
http://www.dextra.com.br/dia-postgresql.htm

Il Corporate Databases 2008 ci sarà il 24 e 25 aprile a Mosca.
http://citforum.ru/seminars/cbd2008/

Il PGCon 2008 ci sarà dal 20 al 23 maggio a Ottawa.
http://www.pgcon.org/2008/

Il PGDay ci sarà a Portland il giorno precedente all'OSCON.
http://pugs.postgresql.org/taxonomy/term/53

La conferenza Open Source 2008 dello stato dell'Utah ha aperto il call
for paper fino al primo giugno.
Questa seconda conferenza annuale ci sarà dal 28 al 30 agosto a Salt Lake City
http://2008.utosc.com/

== 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 ==
Peter Eisentraut committed:

- Implement a few changes to how shared libraries and dynamically
 loadable modules are built.  Foremost, it creates a solid
 distinction between these two types of targets based on what had
 already been implemented and duplicated in ad hoc ways before.
 Specifically, dynamically loadable modules no longer get a soname.
 The numbers previously set in the makefiles were dummy numbers
 anyway, and the presence of a soname upset a few packaging tools, so
 it is nicer not to have one.  The cumbersome detour taken on
 installation (build a libfoo.so.0.0.0 and then override the rule to
 install foo.so instead) is removed.  Lots of duplicated code
 simplified.

- In pgsql/src/Makefile.shlib, always define stlib, since some
 platforms need it for building modules.  Should fix build failures
 on AIX.

- In pgsql/src/Makefile.shlib, on cygwin and win32, don't override the
 shlib name when building a module.  Should fix regression test
 failures on those platforms.

Magnus Hagander committed:

- In pgsql/src/tools/msvc/config.pl, make integer_datetimes the
 default on msvc as well, to have the same default as other
 platforms.

- In pgsql/src/interfaces/libpq/fe-lobj.c, make parameters in
 implementation have same const:ness as the ones in the prototype.
 Silences msvc build warning.

- Create wrapper pgwin32_safestat() and redefine stat() to it on
 win32, because the stat() function in the runtime cannot be trusted
 to always update the st_size field.  Per report and research by
 Sergey Zubkovsky.

Tom Lane committed:

- In pgsql/src/backend/utils/adt/tsvector_op.c, fix
 tsvector_update_trigger() to be domain-friendly: it needs to allow
 all the columns it works with to be domains over the expected type,
 not just exactly the expected type.  In passing, fix ts_stat() the
 same way.  Per report from Markus Wollny.

- Replace "amgetmulti" AM functions with "amgetbitmap", in which the
 whole indexscan always occurs in one call, and the results are
 returned in a TIDBitmap instead of a limited-size array of TIDs.
 This should improve speed a little by reducing AM entry/exit
 overhead, and it is necessary infrastructure if we are ever to
 support bitmap indexes.  In an only slightly related change, add
 support for TIDBitmaps to preserve (somewhat lossily) the knowledge
 that particular TIDs reported by an index need to have their quals
 rechecked when the heap is visited.  This facility is not really
 used yet; we'll need to extend the forced-recheck feature to plain
 indexscans before it's useful, and that hasn't been coded yet.  The
 intent is to use it to clean up 8.3's horrid @@@ kluge for text
 search with weighted queries.  There might be other uses in future,
 but that one alone is sufficient reason.  Heikki Linnakangas, with
 some adjustments by me.

- Fix several datatype input functions that were allowing unused bytes
 in their results to contain uninitialized, unpredictable values.
 While this was okay as far as the datatypes themselves were
 concerned, it's a problem for the parser because occurrences of the
 "same" literal might not be recognized as equal by datumIsEqual (and
 hence not by equal()).  It seems sufficient to fix this in the input
 functions since the only critical use of equal() is in the parser's
 comparisons of ORDER BY and DISTINCT expressions.  Per a trouble
 report from Marc Cousin.  Patch all the way back.  Interestingly,
 array_in did not have the bug before 8.2, which may explain why the
 issue went unnoticed for so long.

- Add some debug support code to try to catch future mistakes in the
 area of input functions that include garbage bytes in their results.
 Provide a compile-time option RANDOMIZE_ALLOCATED_MEMORY to make
 palloc fill returned blocks with variable contents.  This option
 also makes the parser perform conversions of literal constants twice
 and compare the results, emitting a WARNING if they don't match.
 (This is the code I used to catch the input function bugs fixed in
 the previous commit.)  For the moment, I've set it to be activated
 automatically by --enable-cassert.

- A quick try at un-breaking the Cygwin build.  Whether it needs the
 pgwin32_safestat remains to be determined, but in any case the
 current code is not tolerable.

- Create new routines systable_beginscan_ordered,
 systable_getnext_ordered, systable_endscan_ordered that have API
 similar to systable_beginscan etc (in particular, the passed-in
 scankeys have heap not index attnums), but guarantee ordered output,
 unlike the existing functions.  For the moment these are just very
 thin wrappers around index_beginscan/index_getnext/etc.  Someday
 they might need to get smarter; but for now this is just a code
 refactoring exercise to reduce the number of direct callers of
 index_getnext, in preparation for changing that function's API.  In
 passing, remove index_getnext_indexitem, which has been dead code
 for quite some time, and will have even less use than that in the
 presence of run-time-lossy indexes.

- Clean up a few places where Datums were being treated as pointers
 without going through DatumGetPointer or some other "official"
 conversion macro.  Not actually a bug, since Datum the same size as
 pointer is the only supported case at the moment, but good cleanup
 for the future.  Gavin Sherry.

- Turn the -i/--ignore-version options of pg_dump and pg_dumpall into
 no-ops: the server version check is now always enforced.  Relax the
 version check to allow a server that is of pg_dump's own major
 version but a later minor version; this is the only case that -i was
 at all safe to use in.  pg_restore already enforced only a very weak
 version check, so this is really just a documentation change for it.
 Per discussion.

- Phase 2 of project to make index operator lossiness be determined at
 runtime instead of plan time.  Extend the amgettuple API so that the
 index AM returns a boolean indicating whether the indexquals need to
 be rechecked, and make that rechecking happen in nodeIndexscan.c
 (currently the only place where it's expected to be needed; other
 callers of index_getnext are just erroring out for now).  For the
 moment, GIN and GIST have stub logic that just always sets the
 recheck flag to TRUE --- I'm hoping to get Teodor to handle pushing
 that control down to the opclass consistent() functions.  The
 planner no longer pays any attention to amopreqcheck, and that
 catalog column will go away in due course.

- Since createplan.c no longer cares whether index operators are
 lossy, it has no particular need to do get_op_opfamily_properties()
 while building an indexscan plan.  Postpone that lookup until
 executor start.  This simplifies createplan.c a lot more than it
 complicates nodeIndexscan.c, and makes things more uniform since we
 already had to do it that way for RowCompare expressions.  Should be
 a bit faster too, at least for plans that aren't re-used many times,
 since we avoid palloc'ing and perhaps copying the intermediate list
 data structure.

Bruce Momjian committed:

- In FAQ, remove mention of the Berkeley origins of the alias
 "Postgres" --- seems unnecessary to mention in the FAQ, per
 discussion on IRC.

- Revert sentence removal from nickname in FAQ.

- Revert README cleanups.

- Small wording improvements for source code READMEs.

- Update text FAQ.

- In pgsql/doc/src/sgml/backup.sgml, document that continuous
 archiving backup can be used for cases where you can't get a
 simultaneous snapshot.

- Add TODO URLs moved from open items queue.

- Fix main README typo.  Brendan Jurd.

- In TODO, update URLs for dead space map.

- Add TODO: "Support procedures, which return no value."

- Update TODO wording to read: "Allow calling of a procedure outside a
 SELECT that can control the transaction state."

Michael Meskes committed:

- In ecpg, PGTYPEStimestamp_sub should use the values and not the
 pointers to substract.

Alvaro Herrera committed:

- Mention pg_backend_pid() in the system information section in
 addition to the monitoring section.  Jim Nasby

- In pgsql/doc/src/sgml/plperl.sgml, remove mention of DBD::PgSPI,
 which is unmaintained and generally unnecessary.

Marc Fournier committed:

- Add a global cvsignore know, currently just with objfiles.txt in it.


== Patch rigettate (per ora) ==
Andrew Chernow's libpq Win32 mutex performance patch.  Needs
revisions.

Bruce Momjian's patch which allows adminstrators to terminate sessions
with SIGTERM.  It doesn't handle the case where UDFs trap SIGTERM.

== Patch in attesa ==
Magnus Hagander sent in a patch which implements wal_sync_method as an
enum.

Alvaro Herrera sent in another revision of his patch to turn
ActiveSnapshot from a global pointer to a stack.

Zoltan Boszormenyi sent in another revision of his patch to implement
TRUNCATE TABLE with IDENTITY.

Gregory Stark sent in a patch which lets people see EXPLAIN progress
information.

David Fetter sent in a patch which lets psql's \dT see the elements of
enums.

Laurenz Albe sent in another revision of his patch to improve shutdown
during online backup.

Sibte Abbas sent in another revision of his psql slash# command patch.

Andrew Chernow sent in three more revisions of his patch to libpq
which adds a pqtypes hook API.

Brendan Jurd sent in a patch to implement a printTable API for psql
and friends.

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

pgsql-it-generale by date

Next:From: rotellaroDate: 2008-04-19 07:10:51
Subject: Workshop PostgreSQL, strategie di backup e Point in Time Recovery
Previous:From: rotellaroDate: 2008-04-07 07:30:05
Subject: == Postgres Weekly News 06 aprile 2008 ==

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