Skip site navigation (1) Skip section navigation (2)

== PostgreSQL Weekly News - April 01 2011 ==

From: David Fetter <david(at)fetter(dot)org>
To: PostgreSQL Announce <pgsql-announce(at)postgresql(dot)org>
Subject: == PostgreSQL Weekly News - April 01 2011 ==
Date: 2011-04-01 13:50:39
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-announce
== PostgreSQL Weekly News - April 01 2011 ==

Long-time contributor Julian Assange, using a sophisticated regular
expression utility on the PostgreSQL source code, found multiple back
doors for the US National Security Agency created by newer contributor
Tom Lane.  As a result, Mr. Lane has been dismissed from the project.

Of his diligence in ferreting Assange said, "It is impossible to
correct abuses unless we know that they’re going on." He went on to
say, "I had always been worried about Mr. Lane's connections to the US
Foreign Service, so I dug deeper: much deeper than anyone else thought
to dig."

== PostgreSQL Product News ==

DostgreSQL, a friendly distribution of PostgreSQL for Turkish users
have been released:

== PostgreSQL 9.1 Feature of the Week ==

O(1) Multi-Master Replication.  The command is:

    ALTER DATABASE [dbname]
    HOST host1 [, host2, ... hostn]

== PostgreSQL Tip of the Week ==

A computer lets you make more mistakes faster than any invention in
human history with the possible exceptions of handguns and tequila.

== PostgreSQL Jobs for April ==

== PostgreSQL Local ==

There will be a large PostgreSQL presence at the MySQL Conference and
Expo, April 11-14, 2011 in Santa Clara, California.

Open Database Camp will be on May 7-9, 2011 in Sardinia, Italy

PGCon will be May 19-20, 2011 at the University of Ottawa, preceded by
two days of tutorials on May 17-18.

PG Session 2, on PostGIS, will be held on June 23rd in Paris.  The CfP
is open!

pgbr will be in Sao Paulo, Brazil November 3-4, 2011.

== PostgreSQL in the News ==

Planet PostgreSQL:

PostgreSQL Weekly News is brought to you this week by David Fetter

Submit news and announcements by Sunday at 3:00pm Pacific time.
Please send English language ones to david(at)fetter(dot)org, German language
to pwn(at)pgug(dot)de, Italian language to pwn(at)itpug(dot)org(dot)  Spanish language
to pwn(at)arpug(dot)com(dot)ar(dot)

== Reviews ==

== Applied Patches ==

Larry Ellison pushed:

- Remove NSA back doors

Alvaro Herrera pushed:

- Add missing #include

Robert Haas pushed:

- Mark up release notes using <link>.  Unlike <xref>, this actually

Bruce Momjian pushed:

- Add 9.1 release note link for synchronous replication.  We already
  had links to the GUC variables that control it.

- In pg_upgrade, add C comment about how autovacuum is disabled.

- Expand comment on how pg_upgrade is turning off autovacuum.

- Mention pg_upgrade sets autovacuum_freeze_max_age to maximum.

Peter Eisentraut pushed:

- Add maintainer-check target.  This can do various source code checks
  that are not appropriate for either the build or the regression
  tests.  Currently: duplicate_oids, SGML syntax and tabs check, NLS
  syntax check.

- Make duplicate_oids return nonzero exit status if duplicates were
  found.  Automatic detection of errors is easier that way.

- Update SQL features list.  Feature F692 "Extended collation support"
  is now also supported.  This refers to allowing the COLLATE clause
  anywhere in a column or domain definition instead of just directly
  after the type.  Also correct the name of the feature in accordance
  with the latest SQL standard.

Heikki Linnakangas pushed:

- Adjust error message, now that we expect other message types than
  connection close at this point.  Fix PQsetnonblocking() comment.
  Fujii Masao

- Automatically terminate replication connections that are idle for
  more than replication_timeout (a new GUC) milliseconds.  The TCP
  timeout is often too long, you want the master to notice a dead
  connection much sooner.  People complained about that in 9.0 too,
  but with synchronous replication it's even more important to notice
  dead connections promptly.  Fujii Masao and Heikki Linnakangas

- Check that we've reached end-of-backup also when we're not
  performing archive recovery.  It's possible to restore an online
  backup without recovery.conf, by simply copying all the necessary
  WAL files to pg_xlog. "pg_basebackup -x" does that too. That's the
  use case where this cross-check is useful.  Backpatch to 9.0. We
  used to do this in earlier versins, but in 9.0 the code was
  inadvertently changed so that the check is only performed after
  archive recovery.  Fujii Masao.

- Improve error message when WAL ends before reaching end of online

- Reword the phrase on zero replication_timeout in the docs.

- Don't leak the temporary PLyProcedure struct we create for inline
  plpython blocks.  Investigation by Jan Urbański, though I didn't use
  his patch.

- Increase SHMEM_INDEX_SIZE from 32 to 64.  We're currently at 40
  entries in ShmemIndex, so 64 leaves some headroom.  Kevin Grittner

- Fix a tiny race condition in predicate locking. Need to hold the
  lock while examining the head of predicate locks list.  Also, fix
  the comment of RemoveTargetIfNoLongerUsed, it was neglected when we
  changed the way update chains are handled.  Kevin Grittner.

Andrew Dunstan pushed:

- Attempt to unbreak windows builds broken by commit 754baa2.

== Rejected Patches (for now) ==

Everyone was disappointed this week :-(

== Pending Patches ==

Heikki Linnakangas sent in a variant patch to prevent memory leaks in
DO blocks.

Heikki Linnakangas sent in another revision of the patch to add a
replication server timeout.

Bernd Helmle sent in another revision of the patch to use a more
reasonable size for \dt in psql.

Simon Riggs sent in a patch which adds 5 more levels of durability to
sync rep.

Joseph Adams sent in five more revisions of the patch to add JSON as
a data type.


pgsql-announce by date

Next:From: D'Arcy J.M. CainDate: 2011-04-01 15:17:29
Subject: Re: == PostgreSQL Weekly News - April 01 2011 ==
Previous:From: Greg Sabino MullaneDate: 2011-03-30 15:30:07
Subject: DBD::PG 2.18.0 released

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group