Skip to content

Wöchentlicher PostgreSQL Newsletter - 05. August 2007

Der Originalartikel befindet sich unter:

== Wöchentlicher PostgreSQL Newsletter - 05. August 2007 ==

Andreas (ads) Scherbaum ist jetzt verheiratet.

Es gab eine ausgiebige Diskussion über Wikis auf -advocacy.

== PostgreSQL Produkt Neuigkeiten ==

Alinous-Core web/database Sprache erschienen.

pgpool 3.4 und pgpool-II 1.2 erschienen

PostBooks 1.0 erschienen.

== PostgreSQL Jobs im August ==

== PostgreSQL Lokal ==

David Fetter wird dem Septimas Jornadas Regionales de Software
Libre sein.

Wir werden einen Stand, eine BOF und ein Dinner auf der LinuxWorldExpo
haben: Besucht uns! Helft uns aus!

== PostgreSQL in the 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
== Angewandte Patches ==

Magnus Hagander committed:

- Update supported standalone VC++ version to 7.1+ only, and fix some
bad data leftover in win32.mak. Per request from Hiroshi Saito.

Andrew Dunstan committed:

- Move session_start out of MyProcPort stucture and make it a global
called MyStartTime, so that we will be able to create a cookie for
all processes for CSVlogs. It is set wherever MyProcPid is set.
Take the opportunity to remove the now unnecessary session-only
restriction on the %s and %c escapes in log_line_prefix.

- Make sure syslogPipe runs in binary mode on Windows to avoid
corrupting the pipe chunking protocol. Backport to 8.0

Neil Conway committed:

- Tweak for initdb: if more command-line arguments were specified than
expected, exit with an error, rather than complaining about the
error on stderr but continuing onward.

- In pgsql/src/backend/utils/sort/tuplestore.c, fix a memory leak in
tuplestore_end(). Unlikely to be significant during normal
operation, but tuplestore_end() ought to do what it claims to do.

Bruce Momjian committed:

- Mark TODO as done: "Allow buffered WAL writes and fsync."

- In pgsql/src/test/bench/, fix strange quoting.

- In pgsql/src/test/bench/, fix script quoting problem.

- In pgsql/doc/FAQ_MINGW, remove links to old Win32 source code ports.

Tom Lane committed:

- In Fix up bad layout of some comments (probably pg_indent's fault), and
improve grammar a tad. Per Greg Stark.

- Fix crash caused by log_timezone patch if we attempt to emit any
elog messages between the setting of log_line_prefix and the setting
of log_timezone. We can't realistically set log_timezone any
earlier than we do now, so the best behavior seems to be to use GMT
zone if any timestamps are to be logged during early startup.
Create a dummy zone variable with a minimal definition of GMT (in
particular it will never know about leap seconds), so that we can
set it up without reference to any external files.

- Fix a problem in my recent patch to initialize cancel_key for
autovac workers as well as regular backends: if no regular backend
launches before the autovac launcher tries to start an autovac
worker, the postmaster would get an Assert fault due to calling
PostmasterRandom before random_seed was initialized. Cleanest
solution seems to be to take the initialization of random_seed out
of ServerLoop and let PostmasterRandom do it for itself.

- Switch over to using the src/timezone functions for formatting
timestamps displayed in the postmaster log. This avoids
Windows-specific problems with localized time zone names that are in
the wrong encoding, and generally seems like a good idea to
forestall other potential platform-dependent issues. To preserve
the existing behavior that all backends will log in the same time
zone, create a new GUC variable log_timezone that can only be
changed on a system-wide basis, and reference log-related
calculations to that zone instead of the TimeZone variable. This
fixes the issue reported by Hiroshi Saito that timestamps printed by
xlog.c startup could be improperly localized on Windows. We still
need a simpler patch for that problem in the back branches, however.

- Fix some sloppiness in the recent multiple-autovacuum-worker patch.
It was not bothering to initialize is_autovacuum for regular
backends, meaning there was a significant chance of the postmaster
prematurely sending them SIGTERM during database shutdown. Also,
leaving the cancel key unset for an autovac worker meant that any
client could send it SIGINT, which doesn't sound especially good

- Support an optional asynchronous commit mode, in which we don't
flush WAL before reporting a transaction committed. Data
consistency is still guaranteed (unlike setting fsync = off), but a
crash may lose the effects of the last few transactions. Patch by
Simon Riggs, some editorialization by Tom Lane.

- Fix a bug in the original implementation of redundant-join-clause
removal: clauses in which one side or the other references both
sides of the join cannot be removed as redundant, because that
expression won't have been constrained below the join. Per report
from Sergey Burladyan. CVS HEAD does not contain this bug due to
EquivalenceClass rewrite, but it seems wise to include the
regression test for it anyway.

- In pgsql/src/backend/executor/execUtils.c, if we're gonna use
ExecRelationIsTargetRelation here, might as well simplify a bit

- Fix security definer functions with polymorphic arguments. This
case has never worked because fmgr_security_definer() neglected to
pass the fn_expr information through. Per report from Viatcheslav

== Eingesandte Patches ==

Gregory Stark sent in a patch which creates a user-visible function to
make use of convert_to_scalar from SQL.


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