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

== Wöchentlicher PostgreSQL Newsletter - 30. Januar 2011 ==

From: Andreas 'ads' Scherbaum <adsmail(at)wars-nicht(dot)de>
To: "pgsql-de-allgemein(at)postgresql(dot)org" <pgsql-de-allgemein(at)postgresql(dot)org>
Cc: "pgusers(at)postgres(dot)de" <pgusers(at)postgres(dot)de>
Subject: == Wöchentlicher PostgreSQL Newsletter - 30. Januar 2011 ==
Date: 2011-02-01 23:16:02
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-de-allgemein

Der Originalartikel befindet sich unter:

== Wöchentlicher PostgreSQL Newsletter - 30. Januar 2011 ==

NYPUG trifft sich am 15. Februar 2011 um 18:15 Uhr im Yodle Office,
50 W 23rd St, New York, NY. Menr Informationen und Anmeldung unter:

== PostgreSQL Produkt Neuigkeiten ==

DBSolo 4.0, ein SQL Query Werkzeug, das PostgreSQL
unterstützt, ist erschienen.

PostgreSQL Maestro 11.1, ein Windows Administrationswerkzeug
für PostgreSQL, ist erschienen.

OpenSCG PostgreSQL + Java Stacks (Glassfish 3.0.1/PostgreSQL 9.0.2
und Jboss 6.0.0 (GA) / PostgreSQL 9.0.2) sind erschienen.

tail_n_mail 1.17.5, ein Programm zum Überwachen von
Logdateien, ist erschienen.

== PostgreSQL Jobs im Januar ==

== PostgreSQL Lokal ==

Selena Deckelmann wird über die Entwicklung der PostgreSQL
Community am 7. Februar 2010 um 16 Uhr an der Oregon State
University in Corvallis, OR sprechen.

Der vierte jährliche Prager PostgreSQL Development Day findet
am 10. Februar 2011 an der Charles Universität in Prag statt.

Der PostgreSQLFr Call for Projects ist offen. Projekte müssen
PostgreSQL und die französisch-sprechende Community ansprechen.
Maile an appel-projets-2010 AT postgresql DOT fr.

PGDay findet dieses Jahr während der südkalifornischen Linux Ausstellung
(SCALE) im LAX Hilton Hotel in Los Angeles, Kalifornien am Freitag dem
25. Februar 2011 statt. Vorträge kannst du unter pgday-submissions AT
googlegroups DOT com einreichen.

PostgreSQL Conference East 2011: New York,
vom 22. bis 25. März

Das Open Database Camp findet vom 7. bis 9. Mai 2011 in Sardinien,
Italien statt.

PGCon findet am 19. und 20. Mai 2011 an der Universität
von Ottawa statt, vorher gibt es am 17. und 18. Mai
zwei Tage mit Trainings. Der Call for Papers ist offen.

== PostgreSQL in den News ==

Planet PostgreSQL:

Dieser wöchentliche PostgreSQL Newsletter wurde erstellt von David Fetter.

Sende Neuigkeiten und Ankündigungen bis Sonntag, 15 Uhr Pazifischer
Zeit. Bitte sende englische Beiträge an david(at)fetter(dot)org, deutsche an
pwn(at)pgug(dot)de, italienische an pwn(at)itpug(dot)org, spanische an pwn(at)arpug(dot)com(dot)ar(dot)

== Reviews ==

ITAGAKI Takahiro reviewed the log_csv_options patch.

Fujii Masao reviewed the patch to allow base backup to include WALs.

ITAGAKI Takahiro reviewed the patch to support EXTENSIONs in pg_dump.

Jeff Davis reviewed the patch to add truly SERIALIZABLE transactions.

Steve Singer reviewed the patch to use subtransactions in PL/PythonU.

== Applied Patches ==

Magnus Hagander pushed:

- Exclude sepgsql from MSVC regression testing as well. In passing,
   change exclusion in the build to follow the same pattern as other
   always-excluded modules.;a=commitdiff;h=97520809424d46c55e2faf73b5f09cb64b52f4a5

- Typo fix for MemSet size.  Fujii Masao.;a=commitdiff;h=966d4f52c258aba8187d61fdc1e10b80d560f07c

- Use GSSAPI library for SSPI auth, when native SSPI is not available.
   This allows non-Windows clients to connect to a Windows server with
   SSPI authentication.  Christian Ullrich, largely modified by me;a=commitdiff;h=4ea1a273fbc20b29ba4aacd3c21030bd62296d7d

- Add option to include WAL in base backup.  When included, this makes
   the base backup a complete working "clone" of the initial database,
   ready to have a postmaster started against it without the need to
   set up any log archiving or similar.  Magnus Hagander, reviewed by
   Fujii Masao and Heikki Linnakangas;a=commitdiff;h=507069de6dbe18c2163f27fbc780673eef8c5622

Heikki Linnakangas pushed:

- Fix typo in the psql \d query handling, so that we use the correct
   query against 9.0 servers.;a=commitdiff;h=74be35b07cf09350168018234026df94184f8991

- Update psql's \copyright to match the text we have in the COPYRIGHT

Robert Haas pushed:

- More documentation cleanup for sepgsql.  Thom Brown and Robert Haas.;a=commitdiff;h=ea2c2641f908cde198a9999100d847078a05385b

- Fix thinko in ALTER FOREIGN TABLE documentation.  Noah Misch.;a=commitdiff;h=558d1c95ae6afb8728f70a150c593f7e7aa5fac1

- Correct ALTER TYPE -> SET DATA TYPE in ALTER TABLE documentation.
   The latter is the correct name of the operation to change the data
   type of a column.  Noah Misch.;a=commitdiff;h=2b2b2ae2aa4a7089aee729e67bb323154da3841a

- Remove arbitrary ALTER TABLE .. ADD COLUMN restriction.  The
   previous coding prevented ALTER TABLE .. ADD COLUMN from being used
   with a non-NULL default in situations where the table's rowtype was
   being used elsewhere.  But this is a completely arbitrary
   restriction since you could do the same operation in multiple steps
   (add the column, add the default, update the table).  Inspired by a
   patch from Noah Misch, though I didn't use his code.;a=commitdiff;h=a06e41deebdf74b8b5109329dc75b2e9d9057962

- Add a comment explaining why we force physical removal of OIDs.
   Noah Misch, slightly revised.;a=commitdiff;h=5c2a7c6e97741564ab4ff336eac8d8227485dd4c

- Restore ALTER TABLE .. ADD COLUMN w/DEFAULT restriction.  This
   reverts commit a06e41deebdf74b8b5109329dc75b2e9d9057962 of
   2011-01-26.  Per discussion, this behavior is not wanted, as it
   would need to change if we ever made composite types support

- Try to avoid running with a full fsync request queue.  When we need
   to insert a new entry and the queue is full, compact the entire
   queue in the hopes of making room for the new entry.  Doing this on
   every insertion might worsen contention on BgWriterCommLock, but
   when the queue it's full, it's far better than allowing the backend
   to perform its own fsync, per testing by Greg Smith as reported in
   Original idea from Greg Smith.  Patch by me.  Review by Chris Browne
   and Greg Smith;a=commitdiff;h=7f242d880b5b5d9642675517466d31373961cf98

Peter Eisentraut pushed:

- Refactor PLy_spi_prepare to save two levels of indentation.  Instead
   of checking whether the arglist is NULL and then if its length is 0,
   do it in one step, and outside of the try/catch block.  Jan Urbański;a=commitdiff;h=52713d02c73926898629e349a9804cd0cae0470b

- Call PLy_spi_execute_fetch_result inside the try/catch block.  This
   way errors from fetching tuples are correctly reported as errors in
   the SPI call.  While at it, avoid palloc(0).  Jan Urbański;a=commitdiff;h=88dcdf9007895b6703dfaf90d15244055384c603

- Document the "S" option for psql's \dn command in the psql help.
   This option was recently introduced, but the documentation in help.c
   was not updated.;a=commitdiff;h=77ff840835bc40693f36281ab394de881cb327eb

- Fix compiler warnings.  Older versions of GCC appear to report these
   with the current standard option set, newer versions need

- autoreconf.  Synchronize with (someone
   must have forgotten to run autoheader or autoreconf), and clean up
   some spurious change in configure introduced by the last commit

- Improve exception usage in PL/Python.  Use the built-in TypeError,
   not SPIError, for errors having to do with argument counts or types.
   Use SPIError, not simply plpy.Error, for errors in
   PLy_spi_execute_plan.  Finally, do not set a Python exception if
   PyArg_ParseTuple failed, as it already sets the correct exception.
   Jan Urbański;a=commitdiff;h=582b5ac62e74a553e72151b321804a7b2e5fed6f

- Do not prefix error messages with the string "PL/Python: " It is
   redundant, given the error context.  Jan Urbański;a=commitdiff;h=5829738868f8d87263b6d31675e08147d8d7c188

- Use -Wformat-security when available.;a=commitdiff;h=8b6f5f25102f9e2503ce18af77b6fd547a2192ca

- Also save the error detail in SPIError. The temporarily broken
   plpython_unicode test shows a case where this is used.  Do remaining
   fix-ups on the expected files at the same time.;a=commitdiff;h=418df3a5dd94d9f02b895f9c161b2435d61e0729

- Translation updates for release 9.0.3, 8.4.7, 8.3.14, 8.2.20.;a=commitdiff;h=7f2d75408b63fab9cc613b3d60d057f6d3ec3adc;a=commitdiff;h=bdf3a806466b18d89bd92b93bd83bc762450d9e1;a=commitdiff;h=e7a1793f55f479e360725a1300d0444a4282d14b;a=commitdiff;h=d5a0bb5acc87ad272508ce0f1d83f581cb634d27

Bruce Momjian pushed:

- In test_open_sync(), writes kilobytes as intended, not by bytes.;a=commitdiff;h=9fc01922831aba350a61844882c229026ca8bf0b

- Use XLOG_BLCKSZ in pg_test_fsync, rather than our own define, but
   verify it is 8k as expected.;a=commitdiff;h=9dd7933937a076ce7573944b8d1d42e618163440

- Use consistent spacing for PGAPPICON Makefile option.;a=commitdiff;h=d7a714828f1a4d09adef68b58674a6266aa8fa03

- Update warning about synchronous-commit durability, per suggestion
   from Robert Haas.;a=commitdiff;h=a91c950658016162020258574fb98aba182a5eac

- Adjust pg_test_fsync to always do XLOG_BLCKSZ-sized writes, rather
   than always 8k writes, per suggestion from Tom Lane.  Also adjust
   open_sync output layout.;a=commitdiff;h=64bc872761bc9bf730307957f09f44a3eabbe3af

- Update sync commit performance documentation to be consistent with
   other non-durable items, per Robert Haas.;a=commitdiff;h=e84730a916bce0635eb78205d2ea4746ee664d68

- Update contrib documention mentions to point to actual documentation
   sections, rather than just calling it "/contrib/module_name".  Also
   update pg_test_fsync build instructions now that it is in /contrib.;a=commitdiff;h=159e3d86292cfec2a2828f9f69ac7a6cb1be242d

- In pg_test_fsync, use K(1024) rather than k(1000) for write size

- Per Peter Eisentraut, use 'kB' for kilobyte, not 'K'.;a=commitdiff;h=4fec63f94e8edb6181eb3e1e25e979062ab17450

- Restructure streaming docs so streaming seems more integrated in the
   paragraphs, per suggestion from Dan Birken.;a=commitdiff;h=81c48aeaa8fd34f90ab6d6f1d56564d34ac4aa59

- Update non-durable docs about non-synchronous-commit allowing
   transaction loss for a _database_ crash.;a=commitdiff;h=b34ee30115fb6b8da8c3024705bd4ba0339212c1

- Properly capitalize documentation headings;  some only had
   initial-word capitalization.;a=commitdiff;h=5d5678d7c3b336a5aacf15d66ac3ebccaab929f2

Tom Lane pushed:

- Replace pg_class.relhasexclusion with pg_index.indisexclusion.
   There isn't any need to track this state on a table-wide basis, and
   trying to do so introduces undesirable semantic fuzziness.  Move the
   flag to pg_index, where it clearly describes just a single index and
   can be immutable after index creation.;a=commitdiff;h=bd1ad1b019cda851a3e925133c056930368e6424

- Remove old claim that ExclusiveLock is sometimes taken on system
   catalogs.  We used to do that on pg_listener, but pg_listener is no
   more.  Also add a bit more documentation for ShareRowExclusive mode.;a=commitdiff;h=5042d16d1210d1a10a896a0fcf81230ff4b0e383

- Change inv_truncate() to not repeat its systable_getnext_ordered()
   scan.  In the case where the initial call of
   systable_getnext_ordered() returned NULL, this function would
   nonetheless call it again.  That's undefined behavior that only by
   chance failed to not give visibly incorrect results.  Put an if-test
   around the final loop to prevent that, and in passing improve some
   comments.  No back-patch since there's no actual failure.  Per
   report from YAMAMOTO Takashi.;a=commitdiff;h=7ab6f2da23516e48174f3f144ee9ef19bdc287fb

- Improve grammar and spelling in durability discussion.;a=commitdiff;h=85f345bec2d7f2ccb67b98b06342c86372ecf3b1

- Update release notes for releases 9.0.3, 8.4.7, 8.3.14, and 8.2.20.;a=commitdiff;h=29d442199ac978b2272d1d96648585943f499fe6

- Don't include <asm/ia64regs.h> unnecessarily.  We only need that
   header when compiling with icc, since the gcc variant of
   ia64_get_bsp() uses in-line assembly code.  Per report from Frank
   Brendel, the header doesn't exist on all IA64 platforms; so don't
   include it unless we need it.;a=commitdiff;h=0ac8c8df85951a6c4815f5e8e0491b6bba4534b7

- Update release notes.  Security: CVE-2010-4015;a=commitdiff;h=aefb8d9198926e9f7717d6420b802ae4b6352293

- Rephrase pg_conversion description to avoid splitting link across
   page.  The link to the CREATE CONVERSION manual page was split
   across a page boundary in the PDF output, leading to "\pdfendlink
   ended up in different nesting level than \pdfstartlink" error while
   building PDFs.  It wouldn't be worth changing text that's undergoing
   active editing to avoid this, since other editing might result in
   moving the link away from the page end anyway.  But this paragraph
   has been static for a long time, so might as well fix it to prevent
   it from being an issue in future.;a=commitdiff;h=20a0f97273e765598420b261685764b40810c812

- Copy-edit a paragraph in the contrib/seg documentation.  Although
   this improves the style, an ulterior motive is to keep the two table
   links from breaking across lines in PDF output, per complaint from
   Josh Kupershmidt.;a=commitdiff;h=b2826ad52d72195317a13c2074a5cd002c98a338

- Make installation.sgml build standalone again.  We must not try to
   link to sections that aren't part of the standalone "make INSTALL"
   build.  Corrects build failure introduced in commit

- Make reduce_outer_joins() smarter about semijoins.
   reduce_outer_joins() mistakenly treated a semijoin like a left join
   for purposes of deciding whether not-null constraints created by the
   join's quals could be passed down into the join's left-hand side
   (possibly resulting in outer-join simplification there).  Actually,
   semijoin works like inner join for this purpose, ie, we do not need
   to see any rows that can't possibly satisfy the quals.  Hence,
   two-line fix to treat semi and inner joins alike.  Per observation
   by Andres Freund about a performance gripe from Yazan Suleiman.
   Back-patch to 8.4, since this oversight has been there since the
   current handling of semijoins was implemented.;a=commitdiff;h=9688c4e6f1516d2fc0db5d200112c4d91538878d

ITAGAKI Takahiro pushed:

- Make 'on' uppercase in a sql example.;a=commitdiff;h=69039ea8b5569caf09b211f46fa9064468fee3b3

Marc Fournier pushed:

- Tag 9.0.3. 8.4.7, 8.3.14, 8.2.20.;a=commitdiff;h=2fb64d857003c91378ba86b03d753a63ebee95b2;a=commitdiff;h=7df910c7d128b775220d529e23813bb4663dba4e;a=commitdiff;h=5370e1a0014e17f0a3c8f65601c3145c824d9b3f;a=commitdiff;h=f62f223b8e7519d741203d71f5bd8fc7693c0b41

Andrew Dunstan pushed:

- Enable building with the Mingw64 compiler.  This can be used to
   build 64 bit Windows binaries, not only on 64 bit Windows but on
   supported cross-compiling hosts including 32 bit Windows, Cygwin,
   Darwin and Linux.;a=commitdiff;h=91812df4ed0facfb90bec3f9430dd5a97d56f695

- Fix typo;a=commitdiff;h=48c9de80283d4bbdf9bec2f2f929b23f1676f8f9

== Abgelehnte Patches (bis jetzt) ==

Marko (johto) Tiikkaja's patch to add filtering details to EXPLAIN.
Not added to enough places -> returned with feedback.

== Eingesandte Patches ==

Pavel Stehule sent in another revision of the patch to add FOREACH ...
IN ARRAY to PL/pgsql.

ITAGAKI Takahiro sent in another revision of the patch to add

Dimitri Fontaine and ITAGAKI Takahiro traded revisions of the patch to
add EXTENSION support to pg_dump.

Magnus Hagander sent in a patch to allow pg_basebackup to send WALs.

Heikki Linnakangas sent in two more revisions of the patch to allow
multiple concurrent base backups.

Noah Misch sent in two more revisions of the patch to turn no-work
table rewrites caused by ALTER TABLE into no-ops.

Kevin Grittner sent in four more revisions of the patch to add true

Fujii Masao sent in a patch to ensure that logging restartpoints also
implies logging WALs created/deleted/recycled, just as log_checkpoints

KaiGai Kohei sent in two more patches to fix the sepgsql contrib

Alex Hunsaker sent in two more revisions of the patch to convert
between PostgreSQL and Perl arrays in PL/Perl.

Jan Urbanski sent in two more revisions of the patch to fix PL/PythonU
table functions.

Kevin Grittner sent in two revisions of a patch to add .gitignore
files appropriate to coverage builds.

Jan Urbanski sent in another revision of the PL/Python validator
function, per review from Hitoshi Harada.

Jan Urbanski sent in five more revisions of the patch to use SPI in
PL/Python subtransactions.

Jan Urbanski sent in another revision of the patch to have PL/PythonU
immediately invalidate functions with composite arguments.

Jan Urbanski sent in another revision of the patch to implement
tracebacks in PL/PythonU.

Jan Urbanski sent in another revision of the patch to implement custom
datatype parsers for PL/PythonU.

Jan Urbanski sent in another revision of the patch to implement custom
exceptions for SPI in PL/PythonU.

Jeff Davis sent in two more revisions of the patch to add range types.

Marko (johto) Tiikkaja sent in another revision of the patch to add
transaction-scope advisory locks.

Andrew Dunstan sent in a patch to get PostgreSQL running on the
Mingw64 toolset on 64-bit Windows7Pro.

Stephen Frost sent in another revision of the patch to allow logging
the current role in CSV.

Alexander Korotkov sent in two more revisions of the patch to add
wildcard searches to the trigram system-supplied module.

Robert Haas sent in another revision of the patch to generate error
code lists automatically.

Joachim Wieland sent in another revision of the patch to allow for
synchronized snapshots per suggestions from Noah Misch.

Kevin Grittner sent in a patch to track trigger depth for 9.2.

Pavel Stehule sent in another patch to add FOREACH ... IN [array] to

Robert Haas sent in another patch to allow logging of aborted vacuums.

Robert Haas sent in another revision of the patch to spread disk

			Andreas 'ads' Scherbaum
Deutsche PostgreSQL User Group:

pgsql-de-allgemein by date

Next:From: Andreas 'ads' ScherbaumDate: 2011-02-07 23:38:45
Subject: == Wöchentlicher PostgreSQL Newsletter - 06. Februar 2011 ==
Previous:From: Andreas 'ads' ScherbaumDate: 2011-02-01 23:02:51
Subject: Re: WARNING: transaction log file "000000010000000000000085" could not be a

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