== Wöchentlicher PostgreSQL Newsletter - 20. Februar 2011 ==

Der Originalartikel befindet sich unter:

http://www.postgresql.org/community/weeklynews/pwn20110220



== Wöchentlicher PostgreSQL Newsletter - 20. Februar 2011 ==

== PostgreSQL Produkt Neuigkeiten ==

pgpool-II 3.0.2, ein Connection Pooler und mehr,
ist erschienen.
http://pgfoundry.org/projects/pgpool/

PL/Proxy 2.2, ein schreib-skalierendes Clusteringsystem für
PostgreSQL, ist erschienen.
http://pgfoundry.org/projects/plproxy/

== PostgreSQL Jobs im Februar ==

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

== PostgreSQL Lokal ==

PGDay findet dieses Jahr während der südkalifornischen Linux Auss=
tellung
(SCALE) im LAX Hilton Hotel in Los Angeles, Kalifornien am Freitag dem
25. Februar 2011 statt.

PostgreSQL Conference East 2011: New York,
vom 22. bis 25. März
http://www.postgresqlconference.org

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

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.
http://www.pgcon.org/2011/

== PostgreSQL in den News ==

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

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

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

Bruce Momjian pushed:

- Clarify documentation for libpq's PQescapeBytea to mention the new
hex format. Modify PQescapeStringConn() docs to be consisent with
other escaping functions. Add mention problems with pre-9.0
versions of libpq using not understanding bytea hex format to the
9.0 release notes. Backpatch to 9.0 docs.
=20
http://git.postgresql.org/pg/commitdiff/5569ae52ae206b3e3541 1df435884cf848a=
e0494

- Adjust pg_upgrade error message, array freeing, and add error check.
=20
http://git.postgresql.org/pg/commitdiff/fe8f15d5d2f42ad1ce6a 0114c12fd3da0f1=
4dd4a

- Fix bug in 9.1 pg_upgrade processing of old/new relations; adjust
debug output.
=20
http://git.postgresql.org/pg/commitdiff/1cc19cc358c23e3c4e04 f9f38776b625d5e=
13965

- In pg_upgrade, no need to initialize global struct values; they are
always zeros. Also no need to free memory before we exit.
=20
http://git.postgresql.org/pg/commitdiff/497e65f822ff33ed964d 1c891ee6de0d97d=
0b2a6

- In documentation example, use concat_values() instead of concat()
because concat() is a built-in function. Erik Rijkers
=20
http://git.postgresql.org/pg/commitdiff/732808c087a84feed474 9ab1e8a63ceeefc=
f449f

- Document that plpgsql upsert example can fail if insert triggers
return unique exception, or if not used in read committed
transaction mode.
=20
http://git.postgresql.org/pg/commitdiff/f87712d208f7dbe447cd 27e92a99f49fd19=
afe94

- Remove doc mention about read committed in upsert example.
=20
http://git.postgresql.org/pg/commitdiff/3472a2b0565ad0302e5e a47e49a95305c2b=
07f64

- Typo fix. Erik Rijkers
=20
http://git.postgresql.org/pg/commitdiff/4f2cfc5bb4c404c24d58 9339d29c210321f=
4b4d7

- Document that text search comparisons happen after text search
configuration rules. Erik Rijkers
=20
http://git.postgresql.org/pg/commitdiff/5bba4948eb835413cc4a 5ca1e2f7255ce4c=
78e69

- Improve text search prefix doc addition.
=20
http://git.postgresql.org/pg/commitdiff/4077980d67a2f27b88a6 bc7531da31cae0e=
d0fb1

- Initialize variable to quiet compiler.
=20
http://git.postgresql.org/pg/commitdiff/964b46d00ec2222c1273 bec3ead369f3e16=
7d482

- Document that an SQL-standard-compliant query that expects a unique
row from information_schema.referential_constraints might return
several in Postgres because we allow duplicate-named constraints in
the same schema.
=20
http://git.postgresql.org/pg/commitdiff/e07ae21f7ec2260c1713 6a7afaa4dbca405=
d9c24

- Documentation update for UTF16 surrogate pairs in UTF8 encoding.
Marko Kreen
=20
http://git.postgresql.org/pg/commitdiff/8c0f1e2762a896e3af89 0b14babd3409fa4=
9e641

- Adjust documentation wording of window function ORDER BY to not
mention avg() because it was inaccurate.
=20
http://git.postgresql.org/pg/commitdiff/d5813488a4ccc78ec3a4 ad0d5da4e6e844a=
f75e8

- Merge two documentation permission chapters into a single chapter.
=20
http://git.postgresql.org/pg/commitdiff/48d25bac9f024f36b43c bba58778adf9ad0=
207c6

Tom Lane pushed:

- Change the naming convention for extension files to use double
dashes. This allows us to have an unambiguous rule for
deconstructing the names of script files and secondary control
files, without having to forbid extension and version names from
containing any dashes. We do have to forbid them from containing
double dashes or leading/trailing dashes, but neither restriction is
likely to bother anyone in practice. Per discussion, this seems
like a better solution overall than the original design.
=20
http://git.postgresql.org/pg/commitdiff/27d5d7ab10086d833e3d f251951cf63c392=
b8bca

- Convert contrib modules to use the extension facility. This isn't
fully tested as yet, in particular I'm not sure that the
"foo--unpackaged--1.0.sql" scripts are OK. But it's time to get
some buildfarm cycles on it. sepgsql is not converted to an
extension, mainly because it seems to require a very nonstandard
installation process. Dimitri Fontaine and Tom Lane.
=20
http://git.postgresql.org/pg/commitdiff/629b3af27d5c2bc9d6e1 6b22b943ad651d4=
ecb56

- Avoid use of CREATE OR REPLACE FUNCTION in extension installation
files. It was never terribly consistent to use OR REPLACE (because
of the lack of comparable functionality for data types, operators,
etc), and experimentation shows that it's now positively pernicious
in the extension world. We really want a failure to occur if there
are any conflicts, else it's unclear what the extension-ownership
state of the conflicted object ought to be. Most of the time,
CREATE EXTENSION will fail anyway because of conflicts on other
object types, but an extension defining only functions can succeed,
with bad results.
=20
http://git.postgresql.org/pg/commitdiff/029fac2264101919b65f b6319bb994f9419=
69471

- Assorted fixups for "unpackaged" conversion scripts. From first
pass of testing. Notably, there seems to be no need for
adminpack--unpackaged--1.0.sql because none of the objects that the
old module creates would ever be dumped by pg_dump anyway (they are
all in pg_catalog).
=20
http://git.postgresql.org/pg/commitdiff/3b61e57f3c352ab97c65 14898d46480b572=
5ebb9

- Support replacing MODULE_PATHNAME during extension script file
execution. This avoids the need to find a way to make PGXS'
.sql.in-to-.sql rule insert the right thing. We'll just deprecate
use of that hack for extensions.
=20
http://git.postgresql.org/pg/commitdiff/e693e97d754ed6812ea1 15170afeae4bf87=
97d3f

- More fixups for "unpackaged" conversion scripts.
=20
http://git.postgresql.org/pg/commitdiff/de06cfe834dfff283ded dfe1eb2945ba8a4=
fde2a

- Remove no-longer-needed special case hacks in MSVC build scripts.
=20
http://git.postgresql.org/pg/commitdiff/2ee69ff65de6e8626784 d4a263953158ef4=
80ab4

- Fix obsolete references to old-style contrib installation methods.
=20
http://git.postgresql.org/pg/commitdiff/f1fb4b0e63a677cdc86d e667c75142b88a4=
edb65

- Small improvements to external-projects documentation.
=20
http://git.postgresql.org/pg/commitdiff/cee103da14f470d29c47 827b810da44cdab=
2a0d2

- Rearrange extension-related views as per recent discussion. The
original design of pg_available_extensions did not consider the
possibility of version-specific control files. Split it into two
views: pg_available_extensions shows information that is generic
about an extension, while pg_available_extension_versions shows all
available versions together with information that could be
version-dependent. Also, add an SRF pg_extension_update_paths() to
assist in checking that a collection of update scripts provide sane
update path sequences.
=20
http://git.postgresql.org/pg/commitdiff/555353c0c59ada35ae59 c8a76186e98d123=
fa8b3

- Fix MSVC build scripts for recent extension-related changes.
Untested, but we'll soon see if the buildfarm likes this.
=20
http://git.postgresql.org/pg/commitdiff/01ff8dd7560f2647dccc 3d70f713dd6b27b=
f843e

- Rethink naming of contrib/intagg extension. Initially it was called
int_aggregate after the old SQL file, but since the documentation
just says "intagg" and that's also the directory name, let's conform
to that instead.
=20
http://git.postgresql.org/pg/commitdiff/74883d33730ecb69e6f4 142deb8c5882af1=
27b32

- Fix obsolete comment. Comment about MaxAllocSize was not updated
when the TOAST-header macros were replaced in 8.3 "varvarlena"
changes. Per report from Frederik Ramm.
=20
http://git.postgresql.org/pg/commitdiff/887dd041a65006deeaf5 14f78e4a5012dc6=
f7f7c

- Bring hstore's comment into line with style of other contrib
comments. All the other ones that are primarily a new datatype say
"data type for ", so make this one similar.
=20
http://git.postgresql.org/pg/commitdiff/f5fc1de501d03f639967 0dd16989c5925b9=
191d2

- Add CheckTableNotInUse calls in DROP TABLE and DROP INDEX. Recent
releases had a check on rel->rd_refcnt in heap_drop_with_catalog,
but failed to cover the possibility of pending trigger events at
DROP time. (Before 8.4 we didn't even check the refcnt.) When the
trigger events were eventually fired, you'd get "could not open
relation with OID nnn" errors, as in recent report from strk.
Better to throw a suitable error when the DROP is attempted. Also
add a similar check in DROP INDEX. Back-patch to all supported
branches.
=20
http://git.postgresql.org/pg/commitdiff/eff027c43288d1530767 6b1bd4736ab11f3=
4c407

- Fix corner case for binary upgrade: extension functions in
pg_catalog. Normally, pg_dump summarily excludes functions in
pg_catalog from consideration. However, some extensions may create
functions in pg_catalog (adminpack already does that, and extensions
for procedural languages will likely do it too). In binary-upgrade
mode, we have to dump such functions, or the extension will be
incomplete after upgrading. Per experimentation with adminpack.
=20
http://git.postgresql.org/pg/commitdiff/89c29c033154b717b16d b2ee3c87bdec439=
3b0d4

- Add FOREACH IN ARRAY looping to plpgsql. (I'm not entirely sure
that we've finished bikeshedding the syntax details, but the
functionality seems OK.) Pavel Stehule, reviewed by Stephen Frost
and Tom Lane.
=20
http://git.postgresql.org/pg/commitdiff/6e02755b22ea62775c90 6d29b87b55b38ab=
70bd2

- Make a no-op ALTER EXTENSION UPDATE give just a NOTICE, not ERROR.
This seems a bit more user-friendly.
=20
http://git.postgresql.org/pg/commitdiff/65076269ea54a8cd6e39 f066a208c7d13ac=
eac0a

- Add backwards-compatible declarations of some core GIN support
functions. These are needed to support reloading dumps of 9.0
installations containing contrib/intarray or contrib/tsearch2.
Since not only regular dump/reload but binary upgrade would fail, it
seems worth the trouble to carry these stubs for awhile. Note that
the contrib opclasses referencing these functions will still work
fine, since GIN doesn't actually pay any attention to the declared
signature of a support function.
=20
http://git.postgresql.org/pg/commitdiff/6595dd04d136d5c97ae0 5fc580572c8f000=
42143

- Fix bogus test for hypothetical indexes in
get_actual_variable_range(). That function was supposing that
indexoid == 0 for a hypothetical index, but that is not likely to be
true in any non-toy implementation of an index adviser, since
assigning a fake OID is the only way to know at EXPLAIN time which
hypothetical index got selected. Fix by adding a flag to
IndexOptInfo to mark hypothetical indexes. Back-patch to 9.0 where
get_actual_variable_range() was added. Gurjeet Singh
=20
http://git.postgresql.org/pg/commitdiff/a2095f7fb5a57ea1794f 25d029756d9a140=
fd429

- Fix blatantly uninitialized variable in recent commit. Doesn't
anybody around here pay attention to compiler warnings?
=20
http://git.postgresql.org/pg/commitdiff/93016983d1e8f3aeb508 f1be8daf5ca5de5=
c5b61

- Fix contrib/pg_trgm to have smoother updates from 9.0. Take care of
some loose ends in the update-from-unpackaged script, and apply some
ugly hacks to ensure that it produces the same catalog state as the
fresh-install script. Per discussion, this seems like a safer plan
than having two different catalog states that both call themselves
"pg_trgm 1.0", even if it's not immediately clear that the subtle
differences would ever matter. Also, fix the stub function
gin_extract_trgm() so that it works instead of just bleating.
Needed because this function will get called during a regular dump
and reload, if there are any indexes using its opclass. The user
won't have an opportunity to update the extension till later, so
telling him to do so is unhelpful.
=20
http://git.postgresql.org/pg/commitdiff/4eb49db7ae634fab9af7 437b2e7b6388dfd=
83bd3

- Fix upgrade of contrib/btree_gist from 9.0. The initial version of
the update-from-unpackaged script neglected to include the <>
operators that were added to the opclasses during 9.1. To make this
script produce the same final state as the regular install script,
use the same ALTER OPERATOR FAMILY trick as in pg_trgm.
=20
http://git.postgresql.org/pg/commitdiff/ec65a79db2a423a156cd a8e862d34052d71=
75a86

- Fix upgrade of contrib/intarray and contrib/unaccent from 9.0. Take
care of a couple of discrepancies between what you get from a fresh
install and what the first-draft update-from-unpackaged scripts
produced.
=20
http://git.postgresql.org/pg/commitdiff/0024e348989254d48dc4 afe9beab98a6994=
a791e

- Fix upgrade of contrib/xml2 from 9.0. Update script was being
sloppy about two functions that have been changed since 9.0.
=20
http://git.postgresql.org/pg/commitdiff/de623f33353c96657651 f9c3a6c8756616c=
610e4

- Fix tsmatchsel() to account properly for null rows. ts_typanalyze.c
computes MCE statistics as fractions of the non-null rows, which
seems fairly reasonable, and anyway changing it in released versions
wouldn't be a good idea. But then ts_selfuncs.c has to account for
that. Failure to do so results in overestimates in columns with a
significant fraction of null documents. Back-patch to 8.4 where
this stuff was introduced. Jesper Krogh
=20
http://git.postgresql.org/pg/commitdiff/52b60530f257b1591d8b 72264cd6c0dd9aa=
bfd46

- One more hack to make contrib upgrades from 9.0 match fresh 9.1
installs. intarray and tsearch2 both reference core support
functions in their GIN opclasses, and the signatures of those
functions changed for 9.1. We added backwards-compatible pg_proc
entries for the functions in order to allow 9.0 dump files to be
restored at all, but that hack leaves the opclasses pointing at
pg_proc entries different from what they'd point to if the contrib
modules were installed fresh in 9.1. To forestall any possibility
of future problems, fix the opclasses to match fresh installs via
the expedient of direct UPDATEs on pg_amproc in the
update-from-unpackaged scripts. (Yech ... but the alternatives are
worse, or require far more effort than seems justified right now.)
Note: updating pg_amproc is sufficient because there will be no
pg_depend entries corresponding to these dependencies, since the
referenced functions are all pinned.
=20
http://git.postgresql.org/pg/commitdiff/472f608e436a41865b79 5c999bda3369725=
fa097

- Fix parallel pg_restore to handle comments on POST_DATA items
correctly. The previous coding would try to process all
SECTION_NONE items in the initial sequential-restore pass, which
failed if they were dependencies of not-yet-restored items. Fix by
postponing such items into the parallel processing pass once we have
skipped any non-PRE_DATA item. Back-patch into 9.0; the original
parallel-restore coding in 8.4 did not have this bug, so no need to
change it. Report and diagnosis by Arnd Hannemann.
=20
http://git.postgresql.org/pg/commitdiff/4cff100d7378b65ded11 6c5a9960584c351=
e5fa9

- Un-break building with BTREE_BUILD_STATS. This has been broken for
awhile, but not clear it's worth back-patching. Euler Taveira de
Oliveira
=20
http://git.postgresql.org/pg/commitdiff/82220e883236c214d670 c3f14d943690aa7=
8bc17

- Create the catalog infrastructure for foreign-data-wrapper handlers.
Add a fdwhandler column to pg_foreign_data_wrapper, plus HANDLER
options in the CREATE FOREIGN DATA WRAPPER and ALTER FOREIGN DATA
WRAPPER commands, plus pg_dump support for same. Also invent a new
pseudotype fdw_handler with properties similar to language_handler.
This is split out of the "FDW API" patch for ease of review; it's
all stuff we will certainly need, regardless of any other details of
the FDW API. FDW handler functions will not actually get called
yet. In passing, fix some omissions and infelicities in
foreigncmds.c. Shigeru Hanada, Jan Urbanski, Heikki Linnakangas
=20
http://git.postgresql.org/pg/commitdiff/327e0250716f12fe94b6 2669d25e572b40a=
8fba5

- Implement an API to let foreign-data wrappers actually be
functional. This commit provides the core code and documentation
needed. A contrib module test case will follow shortly. Shigeru
Hanada, Jan Urbanski, Heikki Linnakangas
=20
http://git.postgresql.org/pg/commitdiff/bb742407947ad1cbf193 55d24282380d576=
e7654

- Add contrib/file_fdw foreign-data wrapper for reading files via
COPY. This is both very useful in its own right, and an important
test case for the core FDW support. This commit includes a small
refactoring of copy.c to expose its option checking code as a
separately callable function. The original patch submission
duplicated hundreds of lines of that code, which seemed pretty
unmaintainable. Shigeru Hanada, reviewed by Itagaki Takahiro and
Tom Lane
=20
http://git.postgresql.org/pg/commitdiff/7c5d0ae7078456bfeedb 2103c45b9a32285=
c2631

- Minor logic fix for new levenshtein implementation. Alexander
Korotkov
=20
http://git.postgresql.org/pg/commitdiff/087bd179e63f199105da bc8be0c8aebd087=
a178e

Simon Riggs pushed:

- Add version-sensitive SQL for psql when constraints NOT VALID. Bug
report and fix by Andres Freund.
=20
http://git.postgresql.org/pg/commitdiff/f0b8a79c4bea7bfa8924 5ee03abf994b027=
da411

- PITR can stop at a named restore point when recovery target =3D time
though must not update the last transaction timestamp. Plus comment
and message cleanup for recent named restore point. Fujii Masao,
minor changes by me.
=20
http://git.postgresql.org/pg/commitdiff/5c588be729399af5cb8e c66901e3b578936=
823a3

- Additional required docs for pg_constraint catalog entry. Noted by
Bernd Helmle
=20
http://git.postgresql.org/pg/commitdiff/0ff1b7350984b9e4055e 9d3a37d3b875c06=
63ac4

- Hot Standby feedback for avoidance of cleanup conflicts on standby.
Standby optionally sends back information about oldestXmin of
queries which is then checked and applied to the WALSender's
proc->xmin. GetOldestXmin() is modified slightly to agree with
GetSnapshotData(), so that all backends on primary include WALSender
within their snapshots. Note this does nothing to change the
snapshot xmin on either master or standby. Feedback piggybacks on
the standby reply message. vacuum_defer_cleanup_age is no longer
used on standby, though parameter still exists on primary, since
some use cases still exist. Simon Riggs, review comments from Fujii
Masao, Heikki Linnakangas, Robert Haas
=20
http://git.postgresql.org/pg/commitdiff/bca8b7f16a3e720794cb 0afbdb3733be4f8=
d9c2c

- Separate messages for standby replies and hot standby feedback.
Allow messages to be sent at different times, and greatly reduce the
frequency of hot standby feedback. Refactor to allow additional
message types.
=20
http://git.postgresql.org/pg/commitdiff/06828c5febf3a8f9e94b ce5bd84634ce990=
d299f

- Make a hard state change from catchup to streaming mode. More
useful state change for monitoring purposes, plus a required change
for synchronous replication patch.
=20
http://git.postgresql.org/pg/commitdiff/bc76695c4c44e21aed94 ee2bea81c4cdced=
f1390

Robert Haas pushed:

- Delete stray word from comment.
=20
http://git.postgresql.org/pg/commitdiff/8e1124eeeb128ef87045 debfeb8f24cd6db=
ab874

- Avoid a few more SET DATA TYPE table rewrites. When the new type is
an unconstrained domain over the old type, we don't need to rewrite
the table. Noah Misch and Robert Haas
=20
http://git.postgresql.org/pg/commitdiff/0d90dc16f87bd991d7eb 9f536ca46acef75=
86d95

- Rename max_predicate_locks_per_transaction. The new name,
max_pred_locks_per_transaction, is shorter. Kevin Grittner, per
discussion.
=20
http://git.postgresql.org/pg/commitdiff/6a77e9385eb46829ce80 971bc655df9f3ef=
00d9a

- Assorted corrections to the patch to add WAL receiver replies. Per
reports from Fujii Masao.
=20
http://git.postgresql.org/pg/commitdiff/883a9659faf6e49e314b 264ca32ed764506=
8a409

- pg_ctl promote. Fujii Masao, reviewed by Robert Haas, Stephen
Frost, and Magnus Hagander.
=20
http://git.postgresql.org/pg/commitdiff/4695da5ae97bbb58d274 887fd68edbe88d0=
3ebcb

- WAL receiver shouldn't try to send a reply when dying. Per report
from, and discussion with, Fujii Masao.
=20
http://git.postgresql.org/pg/commitdiff/3a087369c0ea858e56c8 af5072de91778a6=
44383

- Remove rule to build sepgsql-regtest.pp. Instead, document how to
build it manually. Per discussion. KaiGai Kohei, with some
wordsmithing by me.
=20
http://git.postgresql.org/pg/commitdiff/24bc6b3db3579f4c480c 6d0f81f7e50f1e6=
c0180

- Typo fixes. Thom Brown
=20
http://git.postgresql.org/pg/commitdiff/9408783aefee9d58dd9d af53c8d6b24ab22=
6f05b

- Add some words of caution to elog.c. Stephen Frost, somewhat
rewritten by me
=20
http://git.postgresql.org/pg/commitdiff/f196738534baa95badd9 d8f1debb5822240=
ebc6b

- Add client_hostname field to pg_stat_activity. Peter Eisentraut,
reviewed by Steve Singer, Alvaro Herrera, and me.
=20
http://git.postgresql.org/pg/commitdiff/4a25bc145ad5d05da6f0 1c00bae0f576e9e=
17115

- Prevent possible compiler warnings. Simon Riggs reports that
rnode.dbNode and rnode.spcNode were generating unused variable
warnings on gcc 4.4.3 with CFLAGS=3D-O1
=20
http://git.postgresql.org/pg/commitdiff/a3e8486dffc413506b14 eae9dc5d423f6ae=
8324a

Peter Eisentraut pushed:

- Allow make check in PL directories. Also add make check-world
target, and refactor pg_regress invocation code in makefiles a bit.
=20
http://git.postgresql.org/pg/commitdiff/2fd77060a2db814146cf 1f6cf77755a4b4f=
d9a80

- Better support for thread-support flag detection with clang. When
testing the stderr produced by various thread-support flags, also
run a compilation in addition to a link, because clang warns on
certain flags when compiling but not when linking.
=20
http://git.postgresql.org/pg/commitdiff/f0053845326e9eba290c 78162ef355558cd=
2fc46

- Also process psqlrc when running psql -l. This was previously not
very useful, but with many people customizing the linestyle, it is
nice for a consistent appearance.
=20
http://git.postgresql.org/pg/commitdiff/b15fabf997fb3cd5e068 0a6ad7576377774=
aae07

- Fix for warnings-free compilation with Python 3.2. The first
argument of PyEval_EvalCode() was changed from PyCodeObject* to
PyObject* because of PEP 384.
=20
http://git.postgresql.org/pg/commitdiff/66d6b4cb54eb3b192c8f 9087592e53c53c2=
0cf06

- Set psql client encoding from locale by default. Add a new libpq
connection option client_encoding (which includes the existing
PGCLIENTENCODING environment variable), which besides an encoding
name accepts a special value "auto" that tries to determine the
encoding from the locale in the client's environment, using the
mechanisms that have been in use in initdb. psql sets this new
connection option to "auto" when running from a terminal and not
overridden by setting PGCLIENTENCODING. original code by Heikki
Linnakangas, with subsequent contributions by Jaime Casanova, Peter
Eisentraut, Stephen Frost, Ibrar Ahmed
=20
http://git.postgresql.org/pg/commitdiff/02e14562a806a96f3812 0c96421d39dfa73=
94192

- Invalidate PL/Python functions with composite type argument when the
type changes. The invalidation will cause the type information to
be refetched, and everything will work. Jan Urbański, review=
ed by
Alex Hunsaker
=20
http://git.postgresql.org/pg/commitdiff/b05186f8a403c7dcd1bd 974948273f8c00e=
db127

Alvaro Herrera pushed:

- Make pg_upgrade compile again
=20
http://git.postgresql.org/pg/commitdiff/8b2557553c6eeba97d9e bf6f048369cabd2=
5c2b6

- Cleanup ClusterInfo initialization in pg_upgrade
=20
http://git.postgresql.org/pg/commitdiff/b4a7e5980b2919d4d2a8 49d046a8e3a77e0=
6fdb7

- Use $INDENT rather than indent throughout the pgindent code. This
allows the user to change the path to be used more easily. Also,
change URL in README.
=20
http://git.postgresql.org/pg/commitdiff/c4d124365b9b535e8c98 e4568ade3e0c15b=
11810

- Convert Postgres arrays to Perl arrays on PL/perl input arguments.
More generally, arrays are turned in Perl array references, and row
and composite types are turned into Perl hash references. This is
done recursively, in a way that's natural to every Perl programmer.
To avoid a backwards compatibility hit, the string representation of
each structure is also available if the function requests it.
Authors: Alexey Klyukin and Alex Hunsaker. Some code cleanups by
me.
=20
http://git.postgresql.org/pg/commitdiff/87bb2ade2ce646083f39 d5ab3e330749021=
1ad04

- pgindent run on plperl.c
=20
http://git.postgresql.org/pg/commitdiff/f7b51d175a02a3b6589f 091ca7329596188=
44232

- Use $INDENT instead of `which` to find the indent binary. Per
discussion after my commit o yesterday.
=20
http://git.postgresql.org/pg/commitdiff/a5dfc94c9a2e6c0c7e0e d97d22ebff37cf7=
d9038

ITAGAKI Takahiro pushed:

- Export the external file reader used in COPY FROM as APIs. They are
expected to be used by extension modules like file_fdw. There are
no user-visible changes. Itagaki Takahiro. Reviewed and tested by
Kevin Grittner and Noah Misch.
=20
http://git.postgresql.org/pg/commitdiff/8ddc05fb01ee2c423bf5 613426726351e86=
0d4b4

- Add transaction-level advisory locks. They share the same locking
namespace with the existing session-level advisory locks, but they
are automatically released at the end of the current transaction and
cannot be released explicitly via unlock functions. Marko Tiikkaja,
reviewed by me.
=20
http://git.postgresql.org/pg/commitdiff/62c7bd31c8878dd45c9b 9b2429ab7a12103=
f3590

- Fix an uninitialized field in DR_copy. Shigeru HANADA
=20
http://git.postgresql.org/pg/commitdiff/5c63982af2a5d2da9025 9e878efb43f16ee=
13ce3

Magnus Hagander pushed:

- Properly initialize variables. Kevin Grittner
=20
http://git.postgresql.org/pg/commitdiff/45a6d79b1764a78301ef 008f4561b5e1763=
52331

== Abgelehnte Patches (bis jetzt) ==

No one was disappointed this week :-)

== Eingesandte Patches ==

ITAGAKI Takahiro sent in another revision of the patch to implement
MULTISET.

Stephen Frost and Robert Haas traded revisions of the patch to allow
logging the current role.

Marti Raudsepp sent in another revision of the patch which makes it so
a key lock is only acquired for columns that can be referenced.

Heikki Linnakangas sent in another revision of the patch to add a FDW
API for SQL/MED.

Thom Brown sent in a patch to make array_cat consistent with the ||
operator for arrays with respect to NULLs.

ITAGAKI Takahiro sent in another revision of the patch to implement
transaction-scope advisory locks.

Kevin Grittner sent in two revisions of a patch to fix an issue with
uninitialized structures from the SSI patch.

ITAGAKI Takahiro sent in another revision of the COPY ENCODING patch.

Per feedback from Heikki Linnakangas, Simon Riggs sent in a patch to
add a server_name parameter, plus mechanism to send info from
standby to master. This will help with synchronous replication.

YAMAMOTO Takashi sent in a patch to fix an issue with SSI.

Tom Lane sent in two versions of a patch to fix pg_tgrm's
update-from-unpackaged script.

Mark Kirkwood sent in a WIP patch to allow the backend to constrain
temporary file space.

Tom Lane sent in a WIP patch to update KNN-GiST.

Magnus Hagander sent in another revision of the patch to include
pg_basebackup.

Robert Haas sent in a patch to fix an issue with an assertion failure
on UNLOGGED VIEWs.

Simon Riggs sent in a patch to add server_name for synchronous
replication.

Simon Riggs sent in anothre revision of the patch to allow for
synchronous replication.

Radoslaw Smogura sent in a patch to add void_send and void_receive,
used in COPY ... BINARY.

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