Skip to content

Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008

Der Originalartikel befindet sich unter:

== Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008 ==

Security Updates 8.3 RC1, 8.2.6, 8.1.11, 8.0.15, 7.4.19 and 7.3.21
sind erschienen. Jetzt updaten!

ASQL, eine Data Warehouse Engine basierend aus PostgreSQL, wurde

Devrim GUNDUZ und Darcy Buskermolen haben die PostgreSQL RPM Buildfarm
erstellt. Selbige wird native Binaries für viele RPM-basierende
Distributionen liefern.

Devrim GUNDUZ und Darcy Buskermolen haben ein yum Repository für
PostgreSQL erstellt.

7.3.21 ist das letzte Community Release der 7.3er Serie. Update so
schnell wie möglich von 7.3.

== PostgreSQL Produkt Neuigkeiten ==

Open Technology Group hat jetzt PostGIS und UMN Mapserver Training.

PGCluster 1.7.0rc8 erschienen.

pg_proboscis und pg_typical 0.9.2 erschienen.

PL/Lua 0.2 erschienen.

PL/Proxy 2.0.4 erschienen.

== PostgreSQL Jobs im Januar ==

== PostgreSQL Lokal ==

Was ist neu in PostgreSQL 8.3 - Frühstück mit Bruce Momjian am
24. Januar 2008 in London. Zum Teilnehmen schicke eine Email an
info.emea <AT>

PGCon 2008 wird vom 20-23. Mai in Ottawa sein, Talks werden ab jetzt

Die BSD und PostgreSQL Teams haben einen gemeinsamen Developer Room auf
der FOSDEM 2008 in Brüssel. Wenn du einen Vortrag halten möchtest oder
beim Managing des Rooms helfen möchtest, kontaktiere
Für mehr Informationen siehe:

PostgreSQL Conference East '08 ist am 29. und 30. März an der
Universität von Maryland, College Park. Call for Papers ist jetzt

== PostgreSQL in den News ==

Planet PostgreSQL:

General Bits, Archive und gelegentliche News Artikel:

Dieser wöchentliche PostgreSQL Newsletter wurde erstellt von David

Sende Neuigkeiten und Ankündigungen bis Sonntag, 15 Uhr Pazifischer
Zeit. Bitte sende englische Beiträge an, deutsche an, italienische an

== Angewandte Patches ==

Michael Meskes committed:

- In ecpg, fixed lexer to parse C quotes correctly.

- In ecpg, changed prototype for ECPGdo because some compilers don't
like int/enum aliasing in there.

Magnus Hagander committed:

- In pgsql/src/include/port/win32.h, don't enforce 32-bit time_t for
FRONTEND apps. Fixes standalone builds of libpq in both 32 and
64-bit. Per gripe from Hiroshi Saito.

- In pgsql/src/interfaces/libpq/win32.mak, generate and include
manifest in standalone libpq build on Windows. Hiroshi Saito

Alvaro Herrera committed:

- In pgsql/doc/src/sgml/protocol.sgml, add index entry for
frontend-backend protocol.

Bruce Momjian committed:

- In pgsql/src/tools/RELEASE_CHANGES, mention use of
src/tools/major_release_split for creating back-branch release

- Add URLs to two excellent web pages about SSL API and certificate

- In pgsql/doc/src/sgml/info.sgml, remove mention of /contrib README
files from documentation because files are moved to SGML.

- In pgsql/src/backend/utils/misc/postgresql.conf.sample,
vacuum_cost_limit has a minimum value of 1, not zero; update
postgresql.conf comment to match.

- Add to TODO: "Add ability to trigger on TRUNCATE."

- In pgsql/doc/src/sgml/datatype.sgml, update documentation for
tsvector duplicate elimination.

Neil Conway committed:

- In pgsql/src/backend/nodes/outfuncs.c, fix a minor bug in outfuncs
support for SetOp: dupOperators is an array of Oid, and therefore
should use the "%u" escape sequence rather than "%d".

- In pgsql/src/backend/nodes/outfuncs.c, fix an omission in the
outfuncs.c support for Agg nodes: the grpColIdx and grpOperators
fields were not emitted by _outAgg().

- In pgsql/src/backend/utils/adt/xml.c, minor perf tweak for
_SPI_strdup(): if we're going to call strlen() anyway, it is faster
to memcpy() than to strcpy().

- Fix two places in xml.c that neglected to check the return values of
SPI_prepare() and SPI_cursor_open(), to silence a Coverity warning.

Tom Lane committed:

- Fix assorted security-grade bugs in the regex engine. All of these
problems are shared with Tcl, since it's their code to begin with,
and the patches have been copied from Tcl 8.5.0. Problems:
CVE-2007-4769: Inadequate check on the range of backref numbers
allows crash due to out-of-bounds read. CVE-2007-4772: Infinite
loop in regex optimizer for pattern '($|^)*'. CVE-2007-6067: Very
slow optimizer cleanup for regex with a large NFA representation, as
well as crash if we encounter an out-of-memory condition during NFA
construction. Part of the response to CVE-2007-6067 is to put a
limit on the number of states in the NFA representation of a regex.
This seems needed even though the within-the-code problems have been
corrected, since otherwise the code could try to use very large
amounts of memory for a suitably-crafted regex, leading to potential
DOS by driving the system into swap, activating a kernel OOM killer,
etc. Although there are certainly plenty of ways to drive the
system into effective DOS with poorly-written SQL queries, these
problems seem worth treating as security issues because many
applications might accept regex search patterns from untrustworthy
sources. Thanks to Will Drewry of Google for reporting these
problems. Patches by Will Drewry and Tom Lane. Security:
CVE-2007-4769, CVE-2007-4772, CVE-2007-6067

- Make standard maintenance operations (including VACUUM, ANALYZE,
REINDEX, and CLUSTER) execute as the table owner rather than the
calling user, using the same privilege-switching mechanism already
used for SECURITY DEFINER functions. The purpose of this change is
to ensure that user-defined functions used in index definitions
cannot acquire the privileges of a superuser account that is
performing routine maintenance. While a function used in an index
is supposed to be IMMUTABLE and thus not able to do anything very
interesting, there are several easy ways around that restriction;
and even if we could plug them all, there would remain a risk of
reading sensitive information and broadcasting it through a covert
channel such as CPU usage. To prevent bypassing this security
measure, execution of SET SESSION AUTHORIZATION and SET ROLE is now
forbidden within a SECURITY DEFINER context. Thanks to Itagaki
Takahiro for reporting this vulnerability. Security: CVE-2007-6600

- The original patch to disallow non-passworded connections to
non-superusers failed to cover all the ways in which a connection
can be initiated in dblink. Plug the remaining holes. Also,
disallow transient connections in functions for which that feature
makes no sense (because they are only sensible as part of a sequence
of operations on the same connection). Joe Conway Security:

- Update release notes for security releases. Security:
CVE-2007-4769, CVE-2007-4772, CVE-2007-6067, CVE-2007-6600,

- Stamp release 8.3RC1. Security: CVE-2007-4769, CVE-2007-4772,
CVE-2007-6067, CVE-2007-6600, CVE-2007-6601

- Stamp release 8.2.6. Security: CVE-2007-4769, CVE-2007-4772,
CVE-2007-6067, CVE-2007-6600, CVE-2007-6601

- Stamp release 8.1.11. Security: CVE-2007-4769, CVE-2007-4772,
CVE-2007-6067, CVE-2007-6600, CVE-2007-6601

- Stamp release 8.0.15. Security: CVE-2007-4769, CVE-2007-4772,
CVE-2007-6067, CVE-2007-6600, CVE-2007-6601

- Stamp release 7.4.19. Security: CVE-2007-4769, CVE-2007-4772,
CVE-2007-6067, CVE-2007-6600, CVE-2007-6601

- Stamp release 7.3.21. Security: CVE-2007-4769, CVE-2007-4772,
CVE-2007-6067, CVE-2007-6600, CVE-2007-6601

- In pgsql/src/backend/utils/adt/tsquery.c, remove unnecessary comma
in enum definition ... some C compilers don't like that. Per report
from J6M.

- informix.c was violating the coding rule about not including any
system headers before c.h. Per report from J6M.

- lmgr.c:DescribeLockTag was never taught about virtual xids, per Greg
Stark. Also a couple of minor tweaks to try to future-proof the
code a bit better against future locktag additions.

- Fix some planner issues found while investigating Kevin Grittner's
report of poorer planning in 8.3 than 8.2: 1. After pushing a
constant across an outer join --- ie, given "a LEFT JOIN b ON (a.x =
b.y) WHERE a.x = 42", we can deduce that b.y is sort of equal to 42,
in the sense that we needn't fetch any b rows where it isn't 42 ---
loop to see if any additional deductions can be made. Previous
releases did that by recursing, but I had mistakenly thought that
this was no longer necessary given the EquivalenceClass machinery.
2. Allow pushing constants across outer join conditions even if the
condition is outerjoin_delayed due to a lower outer join. This is
safe as long as the condition is strict and we re-test it at the
upper join. 3. Keep the outer-join clause even if we successfully
push a constant across it. This is necessary in the
outerjoin_delayed case, but even in the simple case, it seems better
to do this to ensure that the join search order heuristics will
consider the join as reasonable to make. Mark such a clause as
having selectivity 1.0, though, since it's not going to eliminate
very many rows after application of the constant condition. 4.
Tweak have_relevant_eclass_joinclause to report that two relations
are joinable when they have vars that are equated to the same
constant. We won't actually generate any joinclause from such an
EquivalenceClass, but again it seems that in such a case it's a good
idea to consider the join as worth costing out. 5. Fix a bug in
select_mergejoin_clauses that was exposed by these changes: we have
to reject candidate mergejoin clauses if either side was equated to
a constant, because we can't construct a canonical pathkey list for
such a clause. This is an implementation restriction that might be
worth fixing someday, but it doesn't seem critical to get it done
for 8.3.

- Fix a bug in 8.2.x that was exposed while investigating Kevin
Grittner's report of poor planning in 8.3: it's unsafe to push a
constant across an outer join when the outer-join condition is
delayed by lower outer joins, unless we recheck the outer-join
condition at the upper outer join. 8.2.x doesn't really have the
ability to tell whether this is the case or not, but fortunately it
doesn't matter --- it seems most desirable to keep the join
condition whether it's entirely redundant or not. However, it's
usually mostly redundant, so force its selectivity to 1.0. It might
be a good idea to back-patch this into 8.1 as well, but I'll refrain
until/unless there's evidence that 8.1 actually fails on any cases
that this would fix.

- Fix CREATE INDEX CONCURRENTLY to not deadlock against an automatic
or manual VACUUM that is blocked waiting to get lock on the table
being indexed. Per report and fix suggestion from Greg Stark.

- In pgsql/src/backend/utils/mb/mbutils.c, remove incorrect (and
ill-advised anyway) pfree's in pg_convert_from and pg_convert_to.
Per bug #3866 from Andrew Gilligan.

- Restructure the shutdown procedure for the archiver process to allow
it to finish archiving everything (when there's no error), and to
eliminate various hazards as best we can. This fixes a previous 8.3
patch that caused the postmaster to kill and then restart the
archiver during shutdown (!?). The new behavior is that the
archiver is allowed to run unmolested until the bgwriter has exited;
then it is sent SIGUSR2 to tell it to do a final archiving cycle and
quit. We only SIGQUIT the archiver if we want a panic stop; this is
important since SIGQUIT will also be sent to any active
archive_command. The postmaster also now doesn't SIGQUIT the stats
collector until the bgwriter is done, since the bgwriter can send
stats messages in 8.3. The postmaster will not exit until both the
archiver and stats collector are gone; this provides some defense
(not too bulletproof) against conflicting archiver or stats
collector processes being started by a new postmaster instance. We
continue the prior practice that the archiver will check for
postmaster death immediately before issuing any archive_command;
that gives some additional protection against conflicting archivers.
Also, modify the archiver process to notice SIGTERM and refuse to
issue any more archive commands if it gets it. The postmaster
doesn't ever send it SIGTERM; we assume that any such signal came
from init and is a notice of impending whole-system shutdown. In
this situation it seems imprudent to try to start new archive
commands --- if they aren't extremely quick they're likely to get
SIGKILL'd by init. All per discussion.

- Fix a conceptual error in my patch of 2007-10-26 that avoided
considering clauseless joins of relations that have unexploited join
clauses. Rather than looking at every other base relation in the
query, the correct thing is to examine the other relations in the
"initial_rels" list of the current make_rel_from_joinlist()
invocation, because those are what we actually have the ability to
join against. This might be a subset of the whole query in cases
where join_collapse_limit or from_collapse_limit or full joins have
prevented merging the whole query into a single join problem. This
is a bit untidy because we have to pass those rels down through a
new PlannerInfo field, but it's necessary. Per bug #3865 from Oleg

- Fix an old error in clause_selectivity: the default selectivity
estimate for unhandled clause types ought to be 0.5, not 1.0. I
fear I introduced this silliness due to misreading the intent of the
very-poorly-structured code that was there when we inherited the
file from Berkeley. The lack of sanity in this behavior was exposed
by an example from Sim Zacks. (Arguably this is a bug fix and
should be back-patched, but I'm a bit hesitant to introduce a
possible planner behavior change in the back branches; it might
detune queries that worked acceptably in the past.) While at it,
make estimation for DistinctExpr do something marginally realistic,
rather than just defaulting.

- The original implementation of polymorphic aggregates didn't really
get the checking of argument compatibility right; although the
problem is only exposed with multiple-input aggregates in which some
arguments are polymorphic and some are not. Per bug #3852 from
Sokolov Yura.

- Fix logical errors in constraint exclusion: we cannot assume that a
CHECK constraint yields TRUE for every row of its table, only that
it does not yield FALSE (a NULL result isn't disallowed). This
breaks a couple of implications that would be true in two-valued
logic. I had put in one such mistake in an 8.2.5 patch: foo IS NULL
doesn't refute a strict operator on foo. But there was another in
the original 8.2 release: NOT foo doesn't refute an expression whose
truth would imply the truth of foo. Per report from Rajesh Kumar
Mallah. To preserve the ability to do constraint exclusion with one
partition holding NULL values, extend
relation_excluded_by_constraints() to check for attnotnull flags,
and add col IS NOT NULL expressions to the set of constraints we
hope to refute.

- In pgsql/src/backend/utils/adt/xml.c, it turns out the
LIBXML_TEST_VERSION macro calls xmlInitParser(). Therefore we must
xmlCleanupParser(), or we risk leaving behind dangling pointers to
whatever memory context is current when xml_init() is called. This
seems to fix bug #3860, though we might still want the more invasive
solution being worked on by Alvaro.

- In pgsql/doc/src/sgml/ddl.sgml, add note pointing out that read-only
commands no longer consume command IDs.

- Fix a regression test that fails if default_text_search_config isn't

- Fix CREATE INDEX CONCURRENTLY so that it won't use synchronized scan
for its second pass over the table. It has to start at block zero,
else the "merge join" logic for detecting which TIDs are already in
the index doesn't work. Hence, extend heapam.c's API so that
callers can enable or disable syncscan. (I put in an option to
disable buffer access strategy, too, just in case somebody needs
it.) Per report from Hannes Dorbath.

- Use an indexscan not a heapscan to search pg_index in
get_pkey_attnames. Noted while looking for heapscans that might
need to start from block zero.

- Fix pgstat_heap() to not be broken by syncscans starting from a
block higher than zero. Same problem as just detected in CREATE

== Abgelehnte Patches (bis jetzt) ==

Erik Rijkers's doc patch for textsearch.sgml on grounds of not
including the tables referred to in the patch.

Alvaro Herrera's patch to fix BUG #3860. The fix should use the
palloc infrastructure instead.

== Eingesandte Patches ==

Tom Lane sent in 3 revisions of a patch intended to fix archiver
shutdown behavior.
  • Twitter
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008 at
  • Facebook
  • Google Bookmarks
  • FriendFeed
  • Digg Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008
  • Bloglines Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008
  • Technorati Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008
  • Fark this: Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008 at YahooMyWeb
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008 at
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008 at
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008 at
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008 at
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008 at
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008 at blogmarks
  • Bookmark Wöchentlicher PostgreSQL Newsletter - 13. Januar 2008 with wists
  • wong it!
  • Bookmark using any bookmark manager!
  • Stumble It!


No Trackbacks


Display comments as Linear | Threaded

No comments

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.
To leave a comment you must approve it via e-mail, which will be sent to your address after submission.
Form options