== WöchentlicherPostgreSQL Newsletter - 05.Oktober 2008

Der Originalartikel befindet sich unter:
http://people.planetpostgresql.org/dfetter/index.php?/archiv es/194-PostgreS=
QL-Weekly-News-October-05-2008.html


== Wöchentlicher PostgreSQL Newsletter - 05. Oktober 2008 ==

Common Table Expressions (WITH [RECURSIVE]) sind jetzt im CVS. Dank an
Yoshiuki Asaba, Tatsuo Ishii, Tom Lane und alle anderen. Weiter testen!

Das PostgreSQL Zertifizierungsprojekt hat eine Umfrage gestartet.
Die Registrierung findet sich unter:
http://www.postgresqlcertification.org/jta

Der zweite Aufruf für Lightning Talks für die PostgreSQL Konferenz
West ist zu finden unter:
http://www.pgcon.us/west08/talk_submission/

Es wird eine Keysigning Party auf dem PGDay geben. Anmeldung unter:
http://www.pgday.org/en/keysigning-party

Die San Francisco PostgreSQL User Group wird sich im oDesk am Dienstag
dem 14. Oktober um 19:30 Uhr treffen. Anmeldung möglichst schnell.
Details finden sich unter:
http://postgresql.meetup.com/1/calendar/8731010/

Die Portland PostgreSQL User Group wird ihr monatliches Treffen am 16.
Oktober 2008 abhalten, Randal Schwarzt von Stonehenge Consulting wird
einen Vortrag über Smalltalk und PostgreSQL Integration geben. Das
Treffen ist um 19 Uhr im Freegeek - 1731 SE 10th Avenue, Portland, OR.
http://pugs.postgresql.org/pdx

== PostgreSQL Produkt Neuigkeiten ==

check_postgres 2.3.0 erschienen.
http://bucardo.org/check_postgres/

== PostgreSQL Jobs im Oktober ==

http://archives.postgresql.org/pgsql-jobs/2008-10/threads.ph p

== PostgreSQL Lokal ==

Die Russische PostgreSQL Usergruppe wird sich am 6. Oktober in Moskau
treffen. Spezielle Gäste werden erwartet, unter anderem Gavin Roy von
MyYearbook.com und Asko Oja und Marko Krenn von Skype.
http://forum.postgresmen.ru/viewtopic.php?f=3D6&t=3D38

Die Highload++ Konferenz wird vom 6.-8- Oktober in Moskau, Russland
statfinden. Gavin Roy, Asko Oja und Maxim Boguk sprechen über
PostgreSQL Dinge.
http://highload.ru

Die PostgreSQL West Konferenz 2008 wird vom 12. bis 12. Oktober in
Portland, State University in Portland, Oregon stattfinden.
http://www.postgresqlconference.org/
Vorträge einzureichen unter:
http://www.postgresqlconference.org/west08/talk_submission/

Das Ohio LinuxFest 2008, welches am 11. Oktober in Columbus
stattfindet, wird dieses Jahr wieder einen PostgreSQL Stand haben.
Kontaktiere melanie AT dunslane DOT net um zu helfen.

Die PostgreSQL User Group Deutschland wird einen Talk und einen
Workshop auf dem Magdeburger Open Source Tag 2008 in Magdeburg,
Deutschland halten.
http://www.open-source-tag.de/

Der Europäische PostgreSQL Tag (PGDay 2008) findet am 17. und 18.
Oktober in Prato, Toskana, Italien statt. Die Registrierung ist offen:
http://register.pgday.org/ http://www.pgday.org/en/

PostgreSQL hat einen Stand auf der LinuxLive, Olymbia, in Londok (GB)
vom 23-25. Oktober 2008. Schreibe Dave Page wenn du teilnehmen möchtes=
t.
dpage AT pgamin DOT org

== PostgreSQL in den News ==

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

Dieser wöchentliche PostgreSQL Newsletter wurde erstellt von David
Fetter, Selena Marie Deckelmann und Andreas (ads) Scherbaum.

Sende Neuigkeiten und Ankündigungen bis Sonntag, 15 Uhr Pazifischer
Zeit. Bitte sende englische Beiträge an david@fetter.org, deutsche an
pwn@pgug.de, italienische an pwn@itpug.org.

== Angewandte Patches ==

Heikki Linnakangas committed:

- Rewrite the FSM. Instead of relying on a fixed-size shared memory
segment, the free space information is stored in a dedicated FSM
relation fork, with each relation (except for hash indexes; they
don't use FSM). This eliminates the max_fsm_relations and
max_fsm_pages GUC options; remove any trace of them from the
backend, initdb, and documentation. Rewrite contrib/pg_freespacemap
to match the new FSM implementation. Also introduce a new variant
of the get_raw_page(regclass, int4, int4) function in
contrib/pageinspect that let's you to return pages from any relation
fork, and a new fsm_page_contents() function to inspect the new FSM
pages.

- In pgsql/src/include/catalog/catversion.h, forgot to bump catalog
version in the commit of FSM rewrite.

- Rewrite pg_freespacemap to match the new FSM implementation. I
missed these changes from the main FSM commit for some reason.

- In pgsql/src/backend/storage/freespace/freespace.c, fix WAL redo of
FSM truncation. We can't call smgrtruncate() during WAL replay,
because it tries to XLogInsert().

- In pgsql/doc/src/sgml/pgfreespacemap.sgml, fix function name in
pg_freespacemap docs. It's "pg_freespace", not "pg_freespacemap".
Reported by Hubert (depesz) Lubaczewski.

- Make the blkno arguments bigints instead of int4s. A signed int4 is
not large enough for block numbers higher than 2^31. The old
pre-FSM-rewrite pg_freespacemap implementation got this right. While
we're at it, remove some unnecessary #includes.

- Add relation fork support to pg_relation_size() function. You can
now pass name of a fork ('main' or 'fsm', at the moment) to
pg_relation_size() to get the size of a specific fork. Defaults to
'main', if none given. While we're at it, modify pg_relation_size
to take a regclass as argument, instead of separate variants taking
oid and name. This change is transparent to typical use where the
table name is passed as a string literal, like
pg_relation_size('table'), but will break queries like
pg_relation_size(namecol), where namecol is of type name. text-type
input still works, and using a non-schema-qualified table name is
not very reliable anyway, so this is unlikely to break anyone's
queries in practice.

Tom Lane committed:

- In pgsql/src/bin/pg_ctl/pg_ctl.c, fix misspelled comment.

- In pgsql/src/bin/pg_ctl/pg_ctl.c, recent patches to pg_ctl broke
"pg_ctl restart" for the case where no command-line options had been
given to the postmaster; and just plain broke it altogether in 8.1
and 8.0. Per report from KaiGai Kohei.

- In pgsql/src/backend/storage/freespace/freespace.c, fix compiler
warning (unportable sprintf usage).

- In pgsql/src/backend/storage/freespace/freespace.c, suppress an
uninitialized-variable warning (not all versions of gcc complain
here, but some do)

- Improve tuplestore.c to support multiple concurrent read positions.
This facility replaces the former mark/restore support but is
otherwise upward-compatible with previous uses. It's expected to be
needed for single evaluation of CTEs and also for window functions,
so I'm committing it separately instead of waiting for either one of
those patches to be finished. Per discussion with Greg Stark and
Hitoshi Harada. Note: I removed nodeFunctionscan's mark/restore
support, instead of bothering to update it for this change, because
it was dead code anyway.

- In pgsql/src/makefiles/pgxs.mk, partial fix for contrib vpath
breakage.

- In pgsql/src/backend/utils/adt/datetime.c, fix improper display of
fractional seconds in interval values when using
--enable-integer-datetimes and a non-ISO datestyle. Ron Mayer.

- In pgsql/doc/src/sgml/Makefile, add a note about how to check for
bare < and & in SGML docs, before the knowledge disappears again.

- Implement SQL-standard WITH clauses, including WITH RECURSIVE.
There are some unimplemented aspects: recursive queries must use
UNION ALL (should allow UNION too), and we don't have SEARCH or
CYCLE clauses. These might or might not get done for 8.4, but even
without them it's a pretty useful feature. There are also a couple
of small loose ends and definitional quibbles, which I'll send a
memo about to pgsql-hackers shortly. But let's land the patch now
so we can get on with other development. Yoshiyuki Asaba, with lots
of help from Tatsuo Ishii and Tom Lane

- Fix markTargetListOrigin() to not fail on a simple-Var reference to
a recursive CTE that we're still in progress of analyzing. Add a
similar guard to the similar code in expandRecordVariable(), and
tweak regression tests to cover this case. Per report from Dickson
S. Guedes.

- Improve behavior of WITH RECURSIVE with an untyped literal in the
non-recursive term. Per an example from Dickson S. Guedes.

- Tweak the overflow checks in integer division functions to complain
if the machine produces zero (rather than the more usual
minimum-possible-integer) for the only possible overflow case. This
has been seen to occur for at least some word widths on some
hardware, and it's cheap enough to check for everywhere. Per
Peter's analysis of buildfarm reports. This could be back-patched,
but in the absence of any gripes from the field I doubt it's worth
the trouble.

- Fix a missed case in int8-exp-three-digits.out, per buildfarm
results.

- Fix the implicit-RTE code to be able to handle implicit RTEs for
CTEs, as well as regular tables. Per discussion, this seems
necessary to meet the principle of least astonishment. In passing,
simplify the error messages in warnAutoRange(). Now that we have
parser error position info for these errors, it doesn't seem very
useful to word the error message differently depending on whether we
are inside a sub-select or not.

- In pgsql/src/tools/msvc/vcregress.pl, experimental patch to see if
it fixes MSVC builds ...

Magnus Hagander committed:

- In pgsql/src/interfaces/libpq/Makefile, link libpq with libgssapi if
configure finds it, as required by at least NetBSD. Markus Schaaf

Peter Eisentraut committed:

- Allow pg_regress to be run outside the build tree. Look for input
files in both input and output dir, to handle vpath builds more
simply.

- Update pg_regress calls in PL checks to handle vpath builds.

- In pgsql/src/makefiles/pgxs.mk, put back the copying of some of the
regression test data files for vpath builds. It is too complicated
to fix in another way for now.

- In pgsql/src/Makefile.global.in, fix coverage targets so that HTML
view is reliably updated when test data changes. Add some
documenting comments.

- Add regression test for macaddr type. Enhance documentation about
accepted input formats.

- Additional string function tests for coverage of oracle_compat.c

- Additional test coverage for boolean type (bool.c)

- Additional test coverage for int8 type (int8.c)
int8-exp-three-digits.out update untested, might need refinement.

- Reverse int8.out and int8-exp-three-digits.out mixup.

- Remove obsolete internal functions istrue, isfalse, isnottrue,
isnotfalse, nullvalue, nonvalue. A long time ago, these were used
to implement the SQL constructs IS TRUE, etc.

- Remove some unportable tests.

Bruce Momjian committed:

- In pgsql/src/backend/access/heap/README.HOT, update README.HOT to
reflect new snapshot tracking and xmin advancement code in 8.4.

== Abgelehnte Patches (bis jetzt) ==

No one was disappointed this week :-)

== Eingesandte Patches ==

Andrew Dunstan sent in another revision of his patch to implement a
parallel pg_restore.

KaiGai Kohei sent in another revision of his SE-PostgreSQL patches.

David Wheeler sent in another revision of tests for the case-
insensitive text (citext) contrib module.

Zdenek Kotala sent in a patch to clean up the code around
PageGetTempPage, per discussion.

Jonah Harris sent in two revisions of a patch to do block-level CRCs.

Magnus Hagander sent in a patch to change the options field of
pg_hba.conf to take name/value pairs instead of a fixed string, adds
map support for kerberos, GSSAPI and SSPI, and unifies error reporting
for "unsupported auth method on this platform" conditions.

Simon Riggs sent in another revision of his patch to make
infrastructure changes for recovery.

Alvaro Herrera sent in a revised version of Simon Riggs's patch to
implement subtransaction commits.

Greg Smith sent in another revision of his patch to add default_val to
pg_settings.

--=20
Andreas 'ads' Scherbaum
Deutsche PostgreSQL User Group: http://www.pgug.de
DPWN: http://andreas.scherbaum.la/blog/categories/18-PWN

--=20
Sent via pgsql-de-allgemein mailing list (pgsql-de-allgemein@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-de-allgemein