== Wöchentlicher PostgreSQL Newsletter - 15. Mai 2011 ==

== Wöchentlicher PostgreSQL Newsletter - 15. Mai 2011 ==

am 16.05.2011 08:46:51 von adsmail

Der Originalartikel befindet sich unter:


== Wöchentlicher PostgreSQL Newsletter - 15. Mai 2011 ==

PostgreSQL Conference China 2011 findet am 15. und 16. Juli 2011
in Guangzhou statt.

Neue Umfrage: auf welchem Could Hosting hast du PostgreSQL laufen?

NYCPUG trifft sich am 25. Mai um 18:30 Uhr und spricht über "PostgreSQL
und MySQL vergleichen". Adresse: 50 W 23rd St, New York, NY, USA.

PDXPUG hostet PgDay am Sonntag, dem 24. Juli 2011, einen Tag
vor der OSCON in Portland, Oregon, USA. Details hier:

== PostgreSQL Produkt Neuigkeiten ==

DBD::Pg 2.18.1, der Perl Treiber für PostgreSQL, ist erschienen.

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

Bucardo 4.4.4, a Postgres multi-master replication system, released.

boxinfo 1.3.3, ein Skript Sammeln von Serverinformationen,
ist erschienen.

MicroOLAP Database Designer 1.8.0-RC für PostgreSQL ist erschienen.

PaGoDump und PaGoRestore 9.0.4 GUI Werkzeuge für
Windows sind erschienen.

psqlODBC 09.00.0300, ein ODBC Treiber für PostgreSQL, ist erschienen.

SQL/PSM, eine Implementierung des gleichnamigen Teils des
SQL-Standards, ist erschienen.

== PostgreSQL Jobs im Mai ==

http://archives.postgresql.org/pgsql-jobs/2011-05/threads.ph p

== PostgreSQL Lokal ==

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.

PG Session 2 über PostGIS findet am 23. Juni in Paris statt.
Der Call for Papers ist jetzt offen.

CHAR(11), die PostgreSQL Konferenz für Clustering, Hochverfügbark=
und Replikation hat jetzt die Registrierung eröffnet.
Die Konferenz findet am 11. und 12. Juli 2011 in Cambridge, UK statt.

PostgreSQL Conference West (#PgWest) findet vom 27. bis 30. September
2011 im San Jose Convention Center in Jan Jose, Kalifornen, USA statt.

PostgreSQL Conference Europe 2011 findet vom 18. bis
21. Oktober in Amsterdam statt.

pgbr findet in Sao Paulo, Brazilien, am 3. und 4. November 2011 statt.

== PostgreSQL in den News ==

Planet PostgreSQL: http://planet.postgresql.org/

Dieser wöchentliche PostgreSQL Newsletter wurde erstellt von David Fet=

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, spanische an pwn@arpug.com.ar.

== Angewandte Patches ==

Bruce Momjian pushed:

- In pg_upgrade, add status message about superuser check.
http://git.postgresql.org/pg/commitdiff/78318d63d7613ca9fe22 06c717c7ccb4000=

- Update documentation to state there is three-value logic, not
three-value boolean logic. Backpatch to 9.0.X since we just got
another bug report about this today.
http://git.postgresql.org/pg/commitdiff/832c095d686e89f6390e 0ff3e91b4c8015c=

- Documentation cleanup for the possible values of the datatype
http://git.postgresql.org/pg/commitdiff/a9cc9df021f43a8ecda0 924236d22a004ba=

- In pg_upgrade, remove suggestion of setting pg_hba.conf to 'trust',
now that we report the libpq connection failure string. Per
suggestion from Robert Haas.
http://git.postgresql.org/pg/commitdiff/5059cf6ebf36bc9731b8 394a1d2c9dba6cb=

- For create/dropdb, only connect once to the server since we now have
a shared description table for pg_database comments. Also update
comments about database name selection.
http://git.postgresql.org/pg/commitdiff/7ff7711919287a93f348 023d77f9611633c=

- Mention "backslash" escape processing change in 9.1 release notes.
http://git.postgresql.org/pg/commitdiff/64cc297dc9875a6feb3a 310038707b6119b=

Tom Lane pushed:

- Remove "make check" target in src/test/isolation/Makefile. This
doesn't work as expected because the isolationtester program
requires libpq to already be installed. While it works when you've
already installed libpq, having to already have done "make install"
defeats most of the point of a check with a temp installation. And
there are weird corner cases if the dynamic linker picks up an old
libpq.so from system library directories. Remove the target (or
more precisely, make it print a helpful message) so people don't
expect the case to work.
http://git.postgresql.org/pg/commitdiff/7886cc73ad12fb9b5a72 9b6c8152f11a309=

- Be more wary in initdb's creation of platform-dependent collations.
Discard any collation aliases that match the built-in pg_collation
entries (ie, "default", "C", "POSIX"). Such aliases would be
refused by a CREATE COLLATION command, but since initdb is injecting
them via a simple INSERT, it has to make the corresponding check for
itself. Per Martin Pitt's report of funny behavior in a machine
that had a bogus "C.UTF-8" locale. Also, use E'' syntax for the
output of escape_quotes, as per its header comment.
http://git.postgresql.org/pg/commitdiff/853c1750f91feaa6a72b 29ae683c955ab6f=

- Adjust documentation with respect to "unknown" timezone setting.
The recent cleanup of GUC assign hooks got rid of the kludge of
using "unknown" as a magic value for timezone and log_timezone. But
I forgot to update the documentation to match, as noted by Martin
http://git.postgresql.org/pg/commitdiff/1453cd8f82139a3e751c 617dc6635f7b1c7=

- Prevent datebsearch() from crashing on base == NULL && nel == 0.
Normally nel == 0 works okay because the initial value of "last"
will be less than "base"; but if "base" is zero then the calculation
wraps around and we have a very large (unsigned) value for "last",
so that the loop can be entered and we get a SIGSEGV on a bogus
pointer. This is certainly the proximate cause of the recent
reports of Windows builds crashing on 'infinity'::timestamp ---
evidently, they're either not setting an active timezonetktbl, or
setting an empty one. It's not yet clear to me why it's only
happening on Windows and not happening on any buildfarm member. But
even if that's due to some bug elsewhere, it seems wise for this
function to not choke on the powerup values of
timezonetktbl/sztimezonetktbl. I also changed the copy of this code
in ecpglib, although I am not sure whether it's exposed to a similar
hazard. Per report and stack trace from Richard Broersma.
http://git.postgresql.org/pg/commitdiff/2e82d0b396473b595a30 f68b37b8dfd41c3=

- Be more explicit about the meaning of the change in
http://git.postgresql.org/pg/commitdiff/ea964a451e51a32b71d0 04d261874adb1e1=

- Clean up parsing of CREATE TRIGGER's argument list. Use ColLabel in
place of ColId, so that reserved words are accepted as if they were
not reserved. Also, remove BCONST and XCONST, which were never
documented as allowed. Allowing those exposes to users an
implementation detail, namely the format in which the lexer outputs
such constants, that seems unwise to expose. No documentation
change needed, since this just makes the code act more like you'd
expect from reading the CREATE TRIGGER man page. Per complaint from
Szymon Guz and subsequent discussion.
http://git.postgresql.org/pg/commitdiff/6fc6686b48bc569b05ce 711d18cf964498b=

- Split PGC_S_DEFAULT into two values, for true boot_val vs computed
default. Failure to distinguish these cases is the real cause
behind the recent reports of Windows builds crashing on
'infinity'::timestamp, which was directly due to failure to
establish a value of timezone_abbreviations in postmaster child
processes. The postmaster had the desired value, but
write_one_nondefault_variable() didn't transmit it to backends. To
fix that, invent a new value PGC_S_DYNAMIC_DEFAULT, and be sure to
use that or PGC_S_ENV_VAR (as appropriate) for "default" settings
that are computed during initialization. (We need both because
there's at least one variable that could receive a value from either
source.) This commit also fixes ProcessConfigFile's failure to
restore the correct default value for certain GUC variables if they
are set in postgresql.conf and then removed/commented out of the
file. We have to recompute and reinstall the value for any GUC
variable that could have received a value from PGC_S_DYNAMIC_DEFAULT
or PGC_S_ENV_VAR sources, and there were a number of oversights.
(That whole thing is a crock that needs to be redesigned, but not
today.) However, I intentionally didn't make it work "exactly right"
for the cases of timezone and log_timezone. The exactly right
behavior would involve running select_default_timezone, which we'd
have to do independently in each postgres process, causing the whole
database to become entirely unresponsive for as much as several
seconds. That didn't seem like a good idea, especially since the
variable's removal from postgresql.conf might be just an accidental
edit. Instead the behavior is to adopt the previously active
setting as if it were default. Note that this patch creates an ABI
break for extensions that use any of the PGC_S_XXX constants;
they'll need to be recompiled.
http://git.postgresql.org/pg/commitdiff/e05b866447899211a0c2 df31bf0671faac4=

- Fix write-past-buffer-end in ldapServiceLookup(). The code to
assemble ldap_get_values_len's output into a single string wrote the
terminating null one byte past where it should. Fix that, and make
some other cosmetic adjustments to make the code a trifle more
readable and more in line with usual Postgres coding style. Also,
free the "result" string when done with it, to avoid a permanent
memory leak. Bug report and patch by Laurenz Albe, cosmetic
adjustments by me.
http://git.postgresql.org/pg/commitdiff/8d0df2048f8c0663b414 40eeaf73e8859c9=

Peter Eisentraut pushed:

- Put options in more alphabetical order
http://git.postgresql.org/pg/commitdiff/94a8fde403d229ccd9c6 67722ab3af72278=

- Add bug report line to pg_upgrade --help output
http://git.postgresql.org/pg/commitdiff/4c78846cb3a0f7017ad9 6d4513f79b1401f=

- Put pg_test_fsync --help and --version output in line with
conventions. Foremost, it should go to stdout.
http://git.postgresql.org/pg/commitdiff/3a8dcd9a1f9bbe364789 95b22de40967c06=

- Add some punctuation
http://git.postgresql.org/pg/commitdiff/87631ac98df2e32cac22 ddee7b9c37813ff=

- Format pg_upgrade --version in line with conventions
http://git.postgresql.org/pg/commitdiff/00fad9f6fef8ed166b18 3ad45a9bd863d96=

Heikki Linnakangas pushed:

- Shut down WAL receiver if it's still running at end of recovery. We
used to just check that it's not running and PANIC if it was, but
that can rightfully happen if recovery stops at recovery target.
http://git.postgresql.org/pg/commitdiff/a0c8514149de92d48a8c f0f1a1458486851=

Alvaro Herrera pushed:

- Fix assorted typos
http://git.postgresql.org/pg/commitdiff/c6eb5740b3c352fb10bf 61bb4465332ae6b=

Robert Haas pushed:

- Kill stray "not".
http://git.postgresql.org/pg/commitdiff/c5ab8425be07f6a866ce 84dc03f87d69244=

- More cleanup of FOREIGN TABLE permissions handling. This commit
fixes psql, pg_dump, and the information schema to be consistent
with the backend changes which I made as part of commit
be90032e0d1cf473bdd99aee94218218f59f29f1, and also includes a
related documentation tweak. Shigeru Hanada, with slight
http://git.postgresql.org/pg/commitdiff/9bb6d9795253bb521f81 c626fea49a704a3=

Andrew Dunstan pushed:

- Build and run isolation test programs under MSVC.
http://git.postgresql.org/pg/commitdiff/840826e36cd40e63a3af 05d9b41dc65250b=

- Add missing check function lookup.
http://git.postgresql.org/pg/commitdiff/20bacc9560b29b33b6ca d4e53c6a77e6c8a=

- Fix bad macro call noticed by MSVC compiler.
http://git.postgresql.org/pg/commitdiff/ec645ef346d2de2fb889 f6b8a8d2fc70a4e=

== Abgelehnte Patches (bis jetzt) ==

No one was disappointed this week :-)

== Eingesandte Patches ==

KaiGai Kohei sent in a patch to implement SECURITY LABELs on shared
database objects.

Merlin Moncure sent in two more revisions of the hint bit cache patch.

Shigeru HANADA sent in a patch to fix some infelicities in foreign
table handling.

Fujii Masao sent in a patch to fix an issue that arose in the attempt
to time-delay standbys.

Peter Geoghegan sent in a PoC patch demonstrating the named pipe
trick on Windows.

Robert Haas sent in another revision of the patch to make visibility
maps crash-safe.

Yeb Havinga sent in a patch to allow domains over composite types.

Bruce Momjian sent in two revisions of a patch to decouple
pg_upgrade's behavior from environment variables.

Peter Geoghegan sent in an updated version of the patch to detect and
alert on the death of the postmaster.

Tom Lane sent in a WIP patch to refactor the Param typmod in PL/pgsql.

Alexey Klyukin sent in a patch to fix a concurrency issue with ALTER

Alexey Klyukin sent in another revision of the patch to make a
validator for configuration files.

Jaime Casanova sent in a patch to improve the interaction of DOMAINs
with CASTing.

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

Sent via pgsql-de-allgemein mailing list (pgsql-de-allgemein@postgresql.org)
To make changes to your subscription: