== Wöchentlicher PostgreSQL Newsletter - 13. März 2011 ==

== Wöchentlicher PostgreSQL Newsletter - 13. März 2011 ==

am 14.03.2011 20:26:13 von adsmail

Der Originalartikel befindet sich unter:


== Wöchentlicher PostgreSQL Newsletter - 13. März 2011 ==

PostgreSQL 9.1alpha4 erschienen, mit einer Menge neuer, guter
Features. Dies ist die letzte geplante Alpha für 9.1
Du kannst sie hier herunterladen:

Neue Umfrage: Welche 9.1 Features findest du am besten?

== PostgreSQL Jobs im März ==

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

== PostgreSQL Lokal ==

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

Es wird eine umfangreiche PostgreSQL Präsenz auf der MySQL Konferenz
und Expo am am 11-14. April 2011 in Santa Clara, Kalifornien, geben.
http://en.oreilly.com/mysql2011/public/schedule/tag/postgres ql

Das Open Database Camp findet vom 7. bis 9. Mai 2011 in Sardinien,
Italien statt.
http://datacharmer.blogspot.com/2011/01/announcing-open-data base-camp-sardi=

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.

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

== Reviews ==

== Angewandte Patches ==

Heikki Linnakangas pushed:

- Silence compiler warning about undefined function when compiling
without assertions.
http://git.postgresql.org/pg/commitdiff/baabf05196922164db80 bdc45fd0660c870=

- Begin error message with lower-case letter.
http://git.postgresql.org/pg/commitdiff/97e3dacd84f185bff864 85f54c665621222=

- Document the DEFERRABLE option in SET TRANSACTION command. Kevin
http://git.postgresql.org/pg/commitdiff/faba108fe4f2491ebc2b 7faf4343f952125=

- If recovery_target_timeline is set to 'latest' and standby mode is
enabled, periodically rescan the archive for new timelines, while
waiting for new WAL segments to arrive. This allows you to set up a
standby server that follows the TLI change if another standby server
is promoted to master. Before this, you had to restart the standby
server to make it notice the new timeline. This patch only scans
the archive for TLI changes, it won't follow a TLI change in
streaming replication. That is much needed too, but it would be a
much bigger patch than I dare to sneak in this late in the release
cycle. There was discussion on improving the sanity checking of the
WAL segments so that the system would notice more reliably if the
new timeline isn't an ancestor of the current one, but that is not
included in this patch. Reviewed by Fujii Masao.
http://git.postgresql.org/pg/commitdiff/1a4ab9ec23f0635a4c15 b069df60b545814=

- Truncate predicate lock manager's SLRU lazily at checkpoint. That's
safer than doing it aggressively whenever the tail-XID pointer is
advanced, because this way we don't need to do it while holding
SerializableXactHashLock. This also fixes bug #5915 spotted by
YAMAMOTO Takashi, and removes an obsolete comment spotted by Kevin
http://git.postgresql.org/pg/commitdiff/4cd3fb6e1244383fc9f7 7906e7162de0559=

- Don't throw a warning if vacuum sees PD_ALL_VISIBLE flag set on a
page that contains newly-inserted tuples that according to our
OldestXmin are not yet visible to everyone. The value returned by
GetOldestXmin() is conservative, and it can move backwards on
repeated calls, so if we see that contradiction between the
PD_ALL_VISIBLE flag and status of tuples on the page, we have to
assume it's because an earlier vacuum calculated a higher OldestXmin
value, and all the tuples really are visible to everyone. We have
received several reports of this bug, with the "PD_ALL_VISIBLE flag
was incorrectly set in relation ..." warning appearing in logs. We
were finally able to hunt it down with David Gould's help to run
extra diagnostics in an environment where this happened frequently.
Also reword the warning, per Robert Haas' suggestion, to not imply
that the PD_ALL_VISIBLE flag is necessarily at fault, as it might
also be a symptom of corruption on a tuple header. Backpatch to
8.4, where the PD_ALL_VISIBLE flag was introduced.
http://git.postgresql.org/pg/commitdiff/93d888232e80e4d676e2 4fe93ae6d27459d=

- Fix overly strict assertion in SummarizeOldestCommittedSxact().
There's a race condition where SummarizeOldestCommittedSxact() is
called even though another backend already cleared out all finished
sxact entries. That's OK, RegisterSerializableTransactionInt() can
just retry getting a news xact slot from the available-list when
that happens. Reported by YAMAMOTO Takashi, bug #5918.
http://git.postgresql.org/pg/commitdiff/46c333a9638b329a3c80 76d978f27c5b05c=

- Fix bugs in the isolation tester flex rules. Tom Lane pointed out
that it was giving a warning: "-s option given but default rule can
be matched". That was because there was no rule to handle newline in
a quoted string. I made that throw an error. Also, line number
tracking was broken, giving incorrect line number on error. Fixed
that too.
http://git.postgresql.org/pg/commitdiff/74a09d92101f36a5fe66 f4f742537089315=

- In ecpg preprocessor, don't try to look up constants in the test for
variable hiding. A constant is not a variable. It worked in most
cases by accident, because we add constants to the global list of
variables (why?), but float constants like 1.23 were interpreted as
struct field references, and not found. Backpatch to 9.0, where the
test for variable hiding was added.
http://git.postgresql.org/pg/commitdiff/30e8b3e58ed56cbc07ae 7cd392ee4b97821=

Tom Lane pushed:

- Zero out vacuum_count and related counters in pgstat_recv_tabstat().
This fixes an oversight in commit=20
of 2010-08-21, as reported by Itagaki Takahiro. Also a couple of
minor cosmetic adjustments.
http://git.postgresql.org/pg/commitdiff/7193a90fc1e3ce0be768 8c1452e813bd0dd=

- Minor copy-editing in CREATE TRIGGER reference page. Per
suggestions from Thom Brown and Robert Haas.
http://git.postgresql.org/pg/commitdiff/f8c0af840d8408624964 7d4415bd35903bf=

- Improve description of inquiry functions that accept regclass. Per
a suggestion from Thom Brown, though this is not his proposed patch.
http://git.postgresql.org/pg/commitdiff/cfcdc99db67172d46a5e 226375fa97e5c5a=

- Add missing keywords to gram.y's unreserved_keywords list. We
really need an automated check for this ... and did VALIDATE really
need to become a keyword at all, rather than picking some other
syntax using existing keywords?
http://git.postgresql.org/pg/commitdiff/3f7d24da16d32ad0fa5a bf04b669e86a7d4=

- Assorted editing for collation documentation. I made a pass over
this to familiarize myself with the feature, and found some things
that could be improved.
http://git.postgresql.org/pg/commitdiff/a612b17120fc011cefcd ec6948b1cc85435=

- A bit more editing for collation documentation.
http://git.postgresql.org/pg/commitdiff/c0dc44ebba0bbce430e7 1adb195ceec6641=

- Adjust the permissions required for COMMENT ON ROLE. Formerly, any
member of a role could change the role's comment, as of course could
superusers; but holders of CREATEROLE privilege could not, unless
they were also members. This led to the odd situation that a
CREATEROLE holder could create a role but then could not comment on
it. It also seems a bit dubious to let an unprivileged user change
his own comment, let alone those of group roles he belongs to. So,
change the rule to be "you must be superuser to comment on a
superuser role, or hold CREATEROLE to comment on non-superuser
roles". This is the same as the privilege check for
creating/dropping roles, and thus fits much better with the rule for
other object types, namely that only the owner of an object can
comment on it. In passing, clean up the documentation for COMMENT a
little bit. Per complaint from Owen Jacobson and subsequent
http://git.postgresql.org/pg/commitdiff/49a08ca1e968860fe02f a3331cc0aba361d=

- Remove collation information from TypeName, where it does not
belong. The initial collations patch treated a COLLATE spec as part
of a TypeName, following what can only be described as brain fade on
the part of the SQL committee. It's a lot more reasonable to treat
COLLATE as a syntactically separate object, so that it can be added
in only the productions where it actually belongs, rather than
needing to reject it in a boatload of places where it doesn't belong
(something the original patch mostly failed to do). In addition
this change lets us meet the spec's requirement to allow COLLATE
anywhere in the clauses of a ColumnDef, and it avoids unfriendly
behavior for constructs such as "foo::type COLLATE collation". To
do this, pull collation information out of TypeName and put it in
ColumnDef instead, thus reverting most of the collation-related
changes in parse_type.c's API. I made one additional structural
change, which was to use a ColumnDef as an intermediate node in
AT_AlterColumnType AlterTableCmd nodes. This provides enough room
to get rid of the "transform" wart in AlterTableCmd too, since the
ColumnDef can carry the USING expression easily enough. Also fix
some other minor bugs that have crept in in the same areas, like
failure to copy recently-added fields of ColumnDef in copyfuncs.c.
While at it, document the formerly secret ability to specify a
misstatements about what the default collation selection will be
when COLLATE is omitted. BTW, the three-parameter form of
format_type() should go away too, since it just contributes to the
confusion in this area; but I'll do that in a separate patch.
http://git.postgresql.org/pg/commitdiff/a051ef699c3ed1f89088 dd6bbc2574f13d0=

- Fix some oversights in distprep and maintainer-clean targets. At
least two recent commits have apparently imagined that a comment in
a Makefile stating that something would be included in the
distribution tarball was sufficient to make it so. They hadn't
bothered to hook into the upper maintainer-clean targets either.
Per bug #5923 from Charles Johnson, in which it emerged that the
9.1alpha4 tarballs are short a few files that should be there.
http://git.postgresql.org/pg/commitdiff/174f65ab00bb8de0f119 a6a60d562b516ba=

- replication/repl_gram.h needs to be cleaned too ...
http://git.postgresql.org/pg/commitdiff/f6587019ed2c2123c00c 18db2d1e857a625=

- Revert addition of third argument to format_type(). Including
collation in the behavior of that function promotes a world view we
do not want. Moreover, it was producing the wrong behavior for
pg_dump anyway: what we want is to dump a COLLATE clause on
attributes whose attcollation is different from the underlying type,
and likewise for domains, and the function cannot do that for us.
Doing it the hard way in pg_dump is a bit more tedious but produces
more correct output. In passing, fix initdb so that the initial
entry in pg_collation is properly pinned. It was droppable before
http://git.postgresql.org/pg/commitdiff/7564654adf07ec26b83c 7effc7f54f7183e=

- Remove duplicate indexterm to silence openjade wrning.
http://git.postgresql.org/pg/commitdiff/ac435a79c88f51be6bf3 eb5df618c2bac61=

- Create an explicit concept of collations that work for any encoding.
Use collencoding =3D -1 to represent such a collation in pg_collation.
We need this to make the "default" entry work sanely, and a later
patch will fix the C/POSIX entries to be represented this way
instead of duplicating them across all encodings. All lookup
operations now search first for an entry that's
database-encoding-specific, and then for the same name with
collencoding =3D -1. Also some incidental code cleanup in
collationcmds.c and pg_collation.c.
http://git.postgresql.org/pg/commitdiff/e3c732a85c0f247617b2 d44ea567f35731b=

- Split CollateClause into separate raw and analyzed node types.
CollateClause is now used only in raw grammar output, and
CollateExpr after parse analysis. This is for clarity and to avoid
carrying collation names in post-analysis parse trees: that's both
wasteful and possibly misleading, since the collation's name could
be changed while the parsetree still exists. Also, clean up
assorted infelicities and omissions in processing of the node type.
http://git.postgresql.org/pg/commitdiff/8acdb8bf9cebc42cee5a a96a2d594756b44=

- Put in some more safeguards against executing a division-by-zero.
Add dummy returns before every potential division-by-zero in int8.c,
because apparently further "improvements" in gcc's optimizer have
enabled it to break functions that weren't broken before. Aurelien
Jarno, via Martin Pitt
http://git.postgresql.org/pg/commitdiff/72330995a52fb7a3fbdc 666aebc0402cdcb=

- On further reflection, we'd better do the same in int.c. We
previously heard of the same problem in int24div(), so there's not a
good reason to suppose the problem is confined to cases involving
http://git.postgresql.org/pg/commitdiff/2a26639a5d76df7f5934 0cfb4313763f878=

- Make all comparisons done for/with statistics use the default
collation. While this will give wrong answers when estimating
selectivity for a comparison operator that's using a non-default
collation, the estimation error probably won't be large; and anyway
the former approach created estimation errors of its own by trying
to use a histogram that might have been computed with some other
collation. So we'll adopt this simplified approach for now and
perhaps improve it sometime in the future. This patch incorporates
changes from Andres Freund to make sure that selfuncs.c passes a
valid collation OID to any datatype-specific function it calls, in
case that function wants collation information. Said OID will now
always be DEFAULT_COLLATION_OID, but at least we won't get errors.
http://git.postgresql.org/pg/commitdiff/696d1f7f064402840a60 b7177a838d1452a=

- Simplify list traversal logic in add_path(). Its mechanism for
recovering after deleting the current list cell was a bit klugy.
Borrow the technique used in other places.
http://git.postgresql.org/pg/commitdiff/a2eb9e0c08ee73208b54 19f5a53a6eba558=

Robert Haas pushed:

- Synchronous replication doc corrections. Thom Brown
http://git.postgresql.org/pg/commitdiff/c74d3aceb99ea6c6d102 109349b514e76e4=

- Reword alpha release note item on SSI. Per Josh Berkus; some
additional explanatory text by me.
http://git.postgresql.org/pg/commitdiff/bcf85e3f44a518eb7bb7 59541189efb6726=

- Create "replication and recovery" section in alpha release notes.
http://git.postgresql.org/pg/commitdiff/51c0124481213eab45db 193929614070da7=

- Update alpha release notes for latest commits.
http://git.postgresql.org/pg/commitdiff/f14ae5f905282109c9a2 571c2048c564004=

- Make alpha release notes more consistent as regards periods.
http://git.postgresql.org/pg/commitdiff/26ed3fdb4553a0e52c85 34292de0f39bfc2=

- Replication README updates. Fujii Masao
http://git.postgresql.org/pg/commitdiff/fcb99609b60012bc2e82 8b8941d5db46f26=

- Add missing index terms for recovery control functions. Fujii Masao
http://git.postgresql.org/pg/commitdiff/1c3b434a0897a727127b 7c4083f2bfa2c9b=

- Emit a LOG message when pausing at the recovery target. Fujii Masao
http://git.postgresql.org/pg/commitdiff/d16e290a8a52d76d01ef 1d70f8c33336942=

- Minor sync rep corrections. Fujii Masao, with a bit of additional
wordsmithing by me.
http://git.postgresql.org/pg/commitdiff/64360987953e450e5309 8e6b79d89c5b80d=

- Remove obsolete comment. In earlier versions of the sync rep patch,
waiters removed themselves from the queue, but now walsender removes
them before doing the wakeup. Report by Fujii Masao.
http://git.postgresql.org/pg/commitdiff/e397d2ee6474865becb8 f99ac2858673678=

- More synchronous replication tweaks. SyncRepRequested() must check
not only the value of the synchronous_replication GUC but also
whether max_wal_senders > 0. Otherwise, we might end up waiting for
sync rep even when there's no possibility of a standby ever managing
to connect. There are some existing cross-checks to prevent this,
but they're not quite sufficient: the user can start the server with
max_wal_senders=3D0, synchronous_standby_names=3D'', and
synchronous_replication=3Doff and then subsequent make
synchronous_standby_names not empty using pg_ctl reload, and then
SET synchronous_standby=3Don, leading to an indefinite hang. Along
the way, rename the global variable for the synchronous_replication
GUC to match the name of the GUC itself, for clarity. Report by
Fujii Masao, though I didn't use his patch.
http://git.postgresql.org/pg/commitdiff/b8bb8dbf20e13087f8e5 7ff4c42e81776ae=

- More synchronous replication typo fixes. Fujii Masao
http://git.postgresql.org/pg/commitdiff/2e019c8611654175780d b488d81cc2dc831=

- Make error handling of synchronous_standby_names consistent. It's
not a good idea to kill the postmaster just because someone muffs
this, and it's not consistent with what we do for other, similar
GUCs. Fujii Masao, with a bit more hacking by me
http://git.postgresql.org/pg/commitdiff/551c07d84ae2f0d3b7dd e68e52322edf9cb=

Peter Eisentraut pushed:

- Fix behavior when raising plpy.Fatal(). It should cause a
elog(FATAL) error, and it fact it was simply causing a elog(ERROR).
Jan Urbański
http://git.postgresql.org/pg/commitdiff/804d13adfd2f66c70d8d 95a606dde621b32=

- Report Python errors from iterators with PLy_elog. This improves
reporting, as the error string now includes the actual Python
exception. As a side effect, this no longer sets the errcode to
ERRCODE_DATA_EXCEPTION, which might be considered a feature, as it's
not documented and not clear why iterator errors should be treated
differently. Jan Urbański.
http://git.postgresql.org/pg/commitdiff/8f76324352986287c048 32f8e6450d4d295=

- Ignore files built by coverage builds.
http://git.postgresql.org/pg/commitdiff/a2f216547740819bdd79 e05039c525350d7=

- Fix parallel make when running make install before make all. In
addition to the all-foo-recurse: all-bar-recurse dependencies that
constraint the order of the rule execution, we need
install-foo-recurse: install-bar-recurse dependencies in case one
runs make install without a make all first, as some people
apparently do.
http://git.postgresql.org/pg/commitdiff/4502c8e1c06164adb7be 526096e91e04d18=

- Add test case for collation mismatch in recursive query. This isn't
very important by itself, but was left on my list of things without
test coverage for the collation feature.
http://git.postgresql.org/pg/commitdiff/3d9f7ec1ffde399accda 096da4df46b178e=

Michael Meskes pushed:

- Added new version of ecpg's parser test script which was written by
Andy Colson.
http://git.postgresql.org/pg/commitdiff/4ff90d9945b2e33662b2 a0af2cad69ae802=

Bruce Momjian pushed:

- Document that char() ignores spaces in non-pattern comparisons, not
in pattern comparisons such as LIKE and regex.
http://git.postgresql.org/pg/commitdiff/7465ae06be4f1dbc9057 5d68d1ffc3351e1=

- Adjust CHAR() doc mention of pattern matching issues for trailing
http://git.postgresql.org/pg/commitdiff/915cd10c164be27dac01 34efb16358f7d75=

- Fix file descriptor leaks in pg_upgrade in failure code paths.
http://git.postgresql.org/pg/commitdiff/d367d41d662c85901172 4745fec592baf94=

- Improve wording of initdb and pg_controldata manual pages.
Gabrielle Roth.
http://git.postgresql.org/pg/commitdiff/8cc55b1c0fbf9a2e01d1 4311716b59d1931=

- Remove '=3D' from initdb switch syntax.
http://git.postgresql.org/pg/commitdiff/c290476cbd2e2d5f8f6c 7c24ebaa5133ec3=

- Document that server single-user mode does not do checkpoints or
other background processing.
http://git.postgresql.org/pg/commitdiff/01752f7bba627c0c38d5 94b27e502380152=

- Mention gcc version in C comment.
http://git.postgresql.org/pg/commitdiff/76fdee31c4ff74b7eae5 965521a85d29381=

- Use '=3D' when documenting long options.
http://git.postgresql.org/pg/commitdiff/ed0327495c4241fad55a 61c0e5d54366c3e=

- Add proper git-external-diff script to src/tools.
http://git.postgresql.org/pg/commitdiff/9d4625ad0b836538618e 324b4ebbc3ba366=

- Clarify what commands are not allowed in SQL functions.
http://git.postgresql.org/pg/commitdiff/678a0d286c2928aa85bc f25e5c3c633e88e=

- Improve SQL function disallowed command wording.
http://git.postgresql.org/pg/commitdiff/2fdd357cae8ac4dc4723 75301bde701b2bf=

- More wording improvements for disallowed SQL function commands.
http://git.postgresql.org/pg/commitdiff/3aa6041db5706821295d a34b47c60b18a0a=

- Reference doc "examples" section for pg_dump options that often need
complex quoting, e.g. -t and -n.
http://git.postgresql.org/pg/commitdiff/26174d5fd0dec01bbbc4 e766ed32b9a50a0=

- Clarify C comment that O_SYNC/O_FSYNC are really the same settting,
as opposed to O_DSYNC.
http://git.postgresql.org/pg/commitdiff/5ca543fb2e2ca5becdb6 505ac22aaf7218e=

- Modify pg_test_fsync to match the behavior of git head in regards to
O_DIRECT behavior.
http://git.postgresql.org/pg/commitdiff/303b7fcd10a34d8c8b4c 3e6e258faeaf107=

- When a smart pg_ctl shutdown fails, mention -m fast as a tip.
http://git.postgresql.org/pg/commitdiff/3f9cf6b336fb93f4e139 43d9e873f5a4a16=

- Add C comment that new new pg_dump -X options are to be created.
http://git.postgresql.org/pg/commitdiff/c3462e413e8700b4710a 6d23252fd095291=

- Remove pg_dump -X options that are only in 9.1 and not needed for
backward compatibility.
http://git.postgresql.org/pg/commitdiff/72bd19dbddaf57863813 77ad3da281572de=

- Change "TIP" to "HINT" to match backend message style, in pg_ctl -m
fast suggestion.
http://git.postgresql.org/pg/commitdiff/f887294ccfad1545f8c9 4e7d486ffdd90a6=

- Add comment to tools/git-external-diff.
http://git.postgresql.org/pg/commitdiff/dae1e5546cdff98d8521 5a461f108f71fd2=

- Document that the parenthesized VACUUM syntax is deprecated, not the
FREEZE functionality.
http://git.postgresql.org/pg/commitdiff/ad44d505917baf35994f 3eabdb42657bf23=

- Document that libpq's PQgetResult() should be called after a fatal
error to fully process errors.
http://git.postgresql.org/pg/commitdiff/06711de9d9d4e122d4e4 c9b801b471e0482=

- Update C comment about O_DIRECT and fsync().
http://git.postgresql.org/pg/commitdiff/7d23e0f803fc0af0ff7b 317a504eba31a51=

- Document that pg_dump --clean might generate some harmless errors on
http://git.postgresql.org/pg/commitdiff/afaed3add89ffe3df422 319c3a76761e186=

- Update kernel docs for Solaris 10. Josh Berkus
http://git.postgresql.org/pg/commitdiff/3896138b7c18c89f57d3 5fcb85a369d8932=

- Fix "unparenthesized" mention in vacuum docs.
http://git.postgresql.org/pg/commitdiff/ea5c4c71f610712a0d49 2fd39a0d9db102b=

- Improve extract(day) documentation with interval values.
http://git.postgresql.org/pg/commitdiff/cbd2811461daf2c6b71d 56048b96374cc2d=

- In plpsql docs, use RAISE rather than undefined log function.
http://git.postgresql.org/pg/commitdiff/35a1964e557ad5993a94 e8b800135f55b63=

- Adds index entries for session_user and pg_describe_object. Removes
extraneous closing parenthesis from pg_describe_object. Puts
pg_describe_object and has_sequence_privilege in correct
alphabetical position in function listing. Thom Brown
http://git.postgresql.org/pg/commitdiff/59bacbe1470b7b3c4382 284301267b18daf=

- Document how listen_addresses can do only IPv4 or IPv6.
http://git.postgresql.org/pg/commitdiff/a1bb5a480df44e518957 abca0de2d04aaba=

- Document that to_char('FM') removes only trailing zeros.
http://git.postgresql.org/pg/commitdiff/ffe92d15d53625d5ae0c 23f4e1984ed4361=

- Update documentation on FreeBSD write cache control.
http://git.postgresql.org/pg/commitdiff/4869d10afc74e9cc7749 42c24b48cef301a=

- In docs, rename "backwards compatibility" to "backward
compatibility" for consistency.
http://git.postgresql.org/pg/commitdiff/7a8f43968add3c69b79c 49ef236d945e643=

- Use macros for time-based constants, rather than constants.
http://git.postgresql.org/pg/commitdiff/3a3f39fdc00c6caa41d7 95475189ac84440=

- Use "backend process" rather than "backend server", where
http://git.postgresql.org/pg/commitdiff/94fe9c0f4e1672ccd830 cb0aa7fd5ccce97=

ITAGAKI Takahiro pushed:

- synchronous_standby_names is a string parameter.
http://git.postgresql.org/pg/commitdiff/1144726d070746a857a1 3af271e2864961a=

- Remove 's' from recovery_target_timeline's' from the release note.
http://git.postgresql.org/pg/commitdiff/48ff3913d6ce42cd090d 17ea6863be46980=

- Cleanup copyright years and file names in the header comments of
some files.
http://git.postgresql.org/pg/commitdiff/2d8de0a50b54cc0ed430 ffa96dc8776dfe9=

== Abgelehnte Patches (bis jetzt) ==

No one was disappointed this week :-)

== Eingesandte Patches ==

Jan Urbanski sent in another flock of patches to fix PL/PythonU.

Fujii Masao sent in another revision of the replication server timeout

Thom Brown sent in two revisions of doc patches for syncrep.

Fujii Masao sent in four revisions of a patch to add a sample
recovery.conf which illustrates the use of recovery control functions.

Gurjeet Singh sent in another revision of the patch to allow psql to
use relative paths for includes, this time with a long option

Noah Misch sent in a patch to add test for FOR KEY LOCK.

Mark Kirkwood sent in another revision of the patch to constrain
backend temporary file space.

Kevin Grittner sent in a patch to reformat the SSI files per pgindent.

Bruce Momjian and Christopher Browne traded patches to make constants
for magic time values.

Robert Haas sent in a patch to enable ALTER TABLE ... ALTER CONSTRAINT
.... VALID, which makes the system check whether the constraint is true
if not already enforced.

Noah Misch sent in a patch to fix an issue with on-the-fly index tuple
deletion and hot standby.

Bruce Momjian sent in a patch to add a comment to the template0

Robert Haas sent in a patch to add the new keywords 9.1 features have

Noah Misch sent in a patch to fix some memory-related bugs he turned
up while testing an instrumented version of PostgreSQL.

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: