Features Download
From: David Fetter <david <at> fetter.org>
Subject: == PostgreSQL Weekly News - September 08 2013 ==
Newsgroups: gmane.comp.db.postgresql.announce
Date: Monday 9th September 2013 03:57:45 UTC (over 3 years ago)
== PostgreSQL Weekly News - September 08 2013 ==

The London PostgreSQL Users' Group will meet on 11 September 2013 to
discuss the new PostgreSQL 9.3.

The fourth edition of the Argentinian PostgreSQL Day will be held on
November 14 2013 in Buenos Aires, Argentina.  The CfP is open.

PGDay Cuba will be in November, 2013.

== PostgreSQL Product News ==

barman 1.2.3, a backup and recovery manager for PostgreSQL, now with
support for the upcoming PostgreSQL 9.3, released.

PG Commander, a GUI made specifically for PostgreSQL on OSX, released.

PostGIS 2.0.4, the industry standard geographic information
system for PostgreSQL, released.

"PostgreSQL Replication", a book, released.

== PostgreSQL Jobs for September ==


== PostgreSQL Local ==

Postgres Open 2013 will be in Chicago, IL, USA, September 16-18.
The list of talks has been posted on the site.

Open Source Software for Business" (OSS4B) 2013 will be held in Prato,     
Tuscany, Italy on September 19 and 20. Registration is open.               

The PostgreSQL Conference China for 2013 will be held October 26-27,
2013 in Hangzhou.  Chinese language information here:

The Italian PGDay (PGDay.IT) will be held on October the 25th in
Prato, Tuscany, Italy, at Monash University Center.
To register to the event or get information about the accepted talks
and schedule please see the official web site: http://2013.pgday.it

pgconf.EU 2013 will be held on Oct 29-Nov 1, 2013 at the Conrad Hotel
in downtown Dublin, Ireland.  Registration is open.

PGConf.DE 2013 will be held November 8th, 2013, at the Rhineland
Industrial Museum in Oberhausen.  The CfP is open through September
15, 2013.

== PostgreSQL in the News ==

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

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 [email protected], German language
to [email protected], Italian language to [email protected]  Spanish language
to [email protected]

== Applied Patches ==

Peter Eisentraut pushed:

- Translation updates

Andrew Dunstan pushed:

- Fix relfrozenxid query in docs to include TOAST tables.  The
  original query ignored TOAST tables which could result in tables
  needing a vacuum not being reported.  Backpatch to all live

Tom Lane pushed:

- Update time zone data files to tzdata release 2013d.  DST law
  changes in Israel, Morocco, Palestine, Paraguay.  Historical
  corrections for Macquarie Island.

- Docs: wording improvements in discussion of timestamp arithmetic.  I
  started out just to fix the broken markup in commit
  1c2085766187031eaeaae7db4785b9e1d4241988, but got distracted by
  copy-editing.  I see Bruce already fixed the markup, but I'll commit
  the wordsmithing anyway.

- Don't fail for bad GUCs in CREATE FUNCTION with
  check_function_bodies off.  The previous coding attempted to
  activate all the GUC settings specified in SET clauses, so that the
  function validator could operate in the GUC environment expected by
  the function body.  However, this is problematic when restoring a
  dump, since the SET clauses might refer to database objects that
  don't exist yet.  We already have the parameter
  check_function_bodies that's meant to prevent forward references in
  function definitions from breaking dumps, so let's change CREATE
  FUNCTION to not install the SET values if check_function_bodies is
  off.  Authors of function validators were already advised not to
  make any "context sensitive" checks when check_function_bodies is
  off, if indeed they're checking anything at all in that mode.  But
  extend the documentation to point out the GUC issue in particular.
  (Note that we still check the SET clauses to some extent; the
  behavior with !check_function_bodies is now approximately equivalent
  to what ALTER DATABASE/ROLE have been doing for awhile with
  context-dependent GUCs.) This problem can be demonstrated in all
  active branches, so back-patch all the way.

- Allow aggregate functions to be VARIADIC.  There's no inherent
  reason why an aggregate function can't be variadic (even VARIADIC
  ANY) if its transition function can handle the case.  Indeed, this
  patch to add the feature touches none of the planner or executor,
  and little of the parser; the main missing stuff was DDL and pg_dump
  support.  It is true that variadic aggregates can create the same
  sort of ambiguity about parameters versus ORDER BY keys that was
  complained of when we (briefly) had both one- and two-argument forms
  of string_agg().  However, the policy formed in response to that
  discussion only said that we'd not create any built-in aggregates
  with varying numbers of arguments, not that we shouldn't allow users
  to do it.  So the logical extension of that is we can allow users to
  make variadic aggregates as long as we're wary about shipping any
  such in core.  In passing, this patch allows aggregate function
  arguments to be named, to the extent of remembering the names in
  pg_proc and dumping them in pg_dump.  You can't yet call an
  aggregate using named-parameter notation.  That seems like a likely
  future extension, but it'll take some work, and it's not what this
  patch is really about.  Likewise, there's still some work needed to
  make window functions handle VARIADIC fully, but I left that for
  another day.  initdb forced because of new aggvariadic field in
  Aggref parse nodes.

- Update comments concerning PGC_S_TEST.  This GUC context value was
  once only used by ALTER DATABASE SET and ALTER USER SET.  That's not
  true anymore, though, so rewrite the comments to be a bit more
  general.  Patch in HEAD only, since this is just an internal
  documentation issue.

Heikki Linnakangas pushed:

- Fix typo in comment.  Also line-wrap an over-wide line in a comment
  that's ignored by pgindent.

- Keep heavily-contended fields in XLogCtlInsert on different cache
  lines.  Performance testing shows that if the insertpos_lck spinlock
  and the fields that it protects are on the same cache line with
  other variables that are frequently accessed, the false sharing can
  hurt performance a lot.  Keep them apart by adding some padding.

- Make catalog cache hash tables resizeable.  If the hash table
  backing a catalog cache becomes too full (fillfactor > 2), enlarge
  it. A new buckets array, double the size of the old, is allocated,
  and all entries in the old hash are moved to the right bucket in the
  new hash.  This has two benefits. First, cache lookups don't get so
  expensive when there are lots of entries in a cache, like if you
  access hundreds of thousands of tables. Second, we can make the
  (initial) sizes of the caches much smaller, which saves memory.
  This patch dials down the initial sizes of the catcaches. The new
  sizes are chosen so that a backend that only runs a few basic
  queries still won't need to enlarge any of them.

Gregory Stark pushed:

- Fix thinko in worker_spi, count(*) returns a bigint. Thanks

Robert Haas pushed:

- docs: Clarify that we also support Solaris versions greater than 10.

- Expose fsync_fname as a public API.  Andres Freund

Bruce Momjian pushed:

- Docs:  add paragraph about date/timestamp subtraction.  per
  suggestion from Francisco Olart

- doc:  Fix SGML markup for date patch

- Remove dead URL mention in OSX startup script.  Backpatch to 9.3.
  Per suggestion from Gavan Schneider

- Add GUC descriptions for compile-time postgresql.conf settings.
  Previous text was "No description available".  Tianyin Xu

- intarray:  return empty zero-dimensional array for an empty array.
  Previously a one-dimensional empty array was returned, but its text
  representation matched a zero-dimensional array, and there is no way
  to dump/reload a one-dimensional empty array.  BACKWARD
  INCOMPATIBILITY.  Per report from Elein Mustain.

Alvaro Herrera pushed:

- Update obsolete comment

Jeff Davis pushed:

- Revert WAL posix_fallocate() patches.  This reverts commit
  269e780822abb2e44189afaccd6b0ee7aefa7ddd and commit
  5b571bb8c8d2bea610e01ae1ee7bc05adcfff528.  Unfortunately, the
  initial patch had insufficient performance testing, and resulted in
  a regression.  Per report by Thom Brown.

- Improve Range Types and Exclusion Constraints example.  Make the
  examples self-contained to avoid confusion. Per bug report 8367 from
  KOIZUMI Satoru.

Kevin Grittner pushed:

- Eliminate pg_rewrite.ev_attr column and related dead code.  Commit
  95ef6a344821655ce4d0a74999ac49dd6af6d342 removed the ability to
  create rules on an individual column as of 7.3, but left some
  residual code which has since been useless.  This cleans up that
  dead code without any change in behavior other than dropping the
  useless column from the catalog.

Noah Misch pushed:

- Don't VALGRIND_PRINTF() each query string.  Doing so was helpful for
  some Valgrind usage and distracting for other usage.  One can
  achieve the same effect by changing log_statement and pointing both
  PostgreSQL and Valgrind logging to stderr.  Per gripe from Andres

Michael Meskes pushed:

- Close file to no leak file descriptor memory. Found by Coverity.

- Return error if allocation of new element was not possible.  Found
  by Coverity.

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Fabrízio de Royes Mello sent in another revision of a patch to add
SEQUENCES to the possible arguments of DISCARD.

Dimitri Fontaine sent in another revision of a patch to implement
extension templates.

Karl O. Pinc sent in another revision of a patch to clarify backup
instructions and concepts in the documentation.

Maksym Boguk sent in a patch to add a national character type.

Cedric Villemain sent in a patch to fix the way PGXS works for certain
extension builds.

Antonin Houska sent in another revision of a patch to allow throttling

Takayuki Tsunakawa sent in a patch to clarify the recovery
documentation as it relates to preserving statistics.

Blake Smith sent in two more revisions of a patch intended to speed up
queries which use a GIN index.

Bruce Momjian sent in two more revisions of a patch to fix some NULL

Bruce Momjian sent in a patch to make a default effective_cache_size
based on the shared_buffers setting.

Zoltan Boszormenyi sent in two more revisions of a patch to use
readahead in ECPG FETCHes.

Pavel Stehule sent in another revision of a patch to improve NUMERIC

Hari Babu sent in a patch to optimize WAL updates on systems with
certain access profiles.

Andres Freund sent in another revision of a patch to speed up catalog
cache lookups.

Andres Freund, as part of the infrastructure for logical change
replication, sent in a pair of patches to: 1. Allow walsenders to
connect to a specific database, and 2.  Log xl_running_xact's at a
higher frequency than checkpoints are done.

Andres Freund, as part of the infrastructure for logical change
replication, sent in a patch to add information about a table's
primary key to the RelationData struct.

Andres Freund, as part of the infrastructure for logical change
replication, sent in a patch to introduce the concept and usage of

Mitsumasa KONDO sent in a WIP patch to use the FALLOC_FL_KEEP_SIZE
flag where appropriate.

KaiGai Kohei sent in a patch to create infrastructure for custom plan

Satoshi Nagayasu sent in another revision of a patch to add statistics
tracking for dirty writes.

MauMau sent in a patch to set the codeset for libc catalog the same
as postgres catalog to ensure that errors don't appear in the form
'???', which is singularly unhelpful.

Bruce Momjian sent in a patch to correct the permissions used in

Alexander Korotkov sent in two revisions of a patch to fix how
picksplit works in the case of NaN values.

Sent via pgsql-announce mailing list ([email protected])
To make changes to your subscription:
CD: 3ms