Magnus Hagander | 28 Aug 15:35 2014
Picon

PGConf.EU 2014 schedule posted - Matt Asay to deliver keynote

PostgreSQL Conference Europe is pleased to announce that the schedule
for the 2014 event, to be held in Madrid from 21st - 24th October, has
now been published at:

http://2014.pgconf.eu/schedule/

As well as a wide range of talks for PostgreSQL users, developers and
decision makers, we’re pleased to announce that our opening keynote
speaker will be Matt Asay, Vice President of Community at MongoDB, who
will discuss how PostgreSQL and NoSQL databases can work together, and
where each shine on their own.

The schedule is, of course, subject to changes, and a few slots are
still empty as we work to confirm the last set of speakers.

PostgreSQL Conference Europe 2014 is the sixth annual PostgreSQL
Conference Europe, previous events having been held in cities such as
Dublin, Prague and Amsterdam attracting hundreds of PostgreSQL
developers and users. For more information and to register, please
visit the website at:

http://2014.pgconf.eu/

A discounted “early bird” registration rate is available until 15th
September. A discount room rate at the conference hotel is available
until 8th September, so we suggest you book your accommodation soon!

We still have seats left at some of the training sessions held the day
before the main conference, taught by PostgreSQL experts from around
the world, that are subject to availability at a first come first
(Continue reading)

David Fetter | 25 Aug 07:30 2014

== PostgreSQL Weekly News - August 24 2014 ==

== PostgreSQL Weekly News - August 24 2014 ==

== PostgreSQL Product News ==

barman 1.3.3, a backup and recovery manager for PostgreSQL, released.
http://www.pgbarman.org/

DBD::Pg version 3.4.0 released (Perl Postgres driver):
http://search.cpan.org/dist/DBD-Pg/

POWA, a PostgreSQL workload analyzer, released.
http://dalibo.github.io/powa/

quince (QUeries In C++ Expressions), a library to access PostgreSQL
from C++, released.
http://quince-lib.com

== PostgreSQL Jobs for August ==

http://archives.postgresql.org/pgsql-jobs/2014-08/threads.php

== PostgreSQL Local ==

PgDay Portland, Oregon 2014 will be held Saturday September 6, 2014.
https://wiki.postgresql.org/wiki/PDXPUGDay2014

Postgres Open 2014 will be in Chicago, IL, USA, September 17-19.
Tickets and Tutorials now available for purchase.
https://postgresopen.org/2014/tickets/
http://postgresopen.org/2014/callforpapers/
(Continue reading)

Gabriele Bartolini | 21 Aug 09:19 2014
Picon

Barman 1.3.3 released

21 August 2014: 2ndQuadrant is proud to announce the release of
version 1.3.3 of Barman, Backup and Recovery Manager for PostgreSQL.

This major release improves robustness of both backup procedures and
their monitoring, by introducing:

  * the so-called "smelly backup" control, allowing DBAs to detect
    possible problems in scheduling of periodical backups, by
    receiving complaints by "barman check" when the latest available
    backup for a server is older than a specified timeframe
  * management of retry attempts for base backup copy (for both
    "barman backup" and "barman recover" commands), making the
    operation more resilient to temporary issues such as network
    connection drops

Performance issues have been fixed in relation to remote recovery
over existing directories (incremental recovery), by invoking
checksum control only when strictly necessary.

Usability has been enhanced through better exception handling, output
and logging messages. PostgreSQL 8.3 is also now supported.

The following major bugs have been fixed:

  * Copies "recovery.conf" during remote "barman recover" (#43)
  * Correctly detect pre/post archive hook scripts (#41)

Minor bugs have also been fixed.

Many thanks for funding towards the development of this release go to
(Continue reading)

Virginie Jourdan | 19 Aug 15:18 2014

Introducing POWA ! A new PostgreSQL Workload Analyzer

Paris, August 19th 2014

DALIBO is proud to present the first release of POWA, a brand new performance tool for PostgreSQL.

Realtime traffic analysis and dynamic graphs

POWA is a workload analyzer that gives a clear view of the current activity of your PostgreSQL servers with a query runtime graph and a block hit/read graph along with a chart of time consuming request over the specified time period.

If you zoom anywhere in one of the graphs, the chart will adjust and show you which queries were running at that time. If you click on a specific query, you will get additional graphs such as read/write time, number of rows affected, local and shared hit, etc.

A bunch of PL functions are also available to access and manage the stats.

Extending pg_stat_statements

Basically PoWA is a PostgreSQL extension designed to historize information given by the pg_stat_statements extension. It provides SQL SRF to gather useful information on a specified time interval.

This first release is ready for production but of course we will continue to improve it. Please install it (or test our demo site) and let's us know what you think of it. Right now what we need most is feedback and new ideas, especially to improve the user experience and the graphic interface...

PoWA is available under the PostgreSQL license. The main code is a PostgreSQL extension written in C and SQL. The user interface is based on Perl and Mojolicious. Obviously the stats are stored in a PostgreSQL database :-)

For the complete list of changes, please checkout the release note on https://github.com/dalibo/powa/blob/master/CHANGELOG.md

Credits

DALIBO would like to thank all the developers who contributed to this release, especially : Marc Cousin for the original idea and Julien Rouhaud for the hard work on the GUI.

POWA is an open project available under the PostgreSQL License. Any contribution to build a better tool is welcome. You just have to send your ideas, features requests or patches using the GitHub tools or directly to powa <at> dalibo.com

Links :



About POWA :

PoWA is PostgreSQL Workload Analyzer that gathers performance stats and provides real-time charts and graph to help monitor and tune your PostgreSQL servers. It is similar to Oracle AWR or SQL Server MDW.

Code & Demo at http://dalibo.github.io/powa/



About DALIBO :

DALIBO is the leading PostgreSQL company in France, providing support, trainings and consulting to its customers since 2005. The company contributes to the PostgreSQL community in various ways, including : code, articles, translations, free conferences and workshops

Check out DALIBO's open source projects at http://dalibo.github.io

http://www.dalibo.com

Michael Shepanski | 19 Aug 00:43 2014
Picon

New wrapper library: QUINCE

Hi PostgreSQLers,

I've released an open-source library called quince (QUeries In C++ 
Expressions) that helps you access PostgreSQL from C++.  I know, I know: 
you've got plenty of those already, but this one is different ...

It's an EDSL (Embedded Domain-Specific Language), which lets you build 
sophisticated SQL queries in C++ syntax with C++ data types, and it's 
also an ORM, which figures out how to represent your C++ 
structs/classes/tuples as multiple columns. It's a plain old library, so 
no special compiler and no code generation step. And fwiw it works with 
sqlite too (and maybe other DBMSes in the future -- it's a matter of 
adding backend libraries).

It's all explained at http://quince-lib.com .

Cheers,
--- Michael Shepanski

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

David Fetter | 18 Aug 07:57 2014

== PostgreSQL Weekly News - August 17 2014 ==

== PostgreSQL Weekly News - August 17 2014 ==

== PostgreSQL Product News ==

pgBadger 6.0, a parallel PostgreSQL log analyzer written in Perl, released:
https://sourceforge.net/projects/pgbadger/
Development:
https://github.com/dalibo/pgbadger/

== PostgreSQL Jobs for August ==

http://archives.postgresql.org/pgsql-jobs/2014-08/threads.php

== PostgreSQL Local ==

PgDay Portland, Oregon 2014 will be held Saturday September 6, 2014.
https://wiki.postgresql.org/wiki/PDXPUGDay2014

Postgres Open 2014 will be in Chicago, IL, USA, September 17-19.
Tickets and Tutorials now available for purchase.
https://postgresopen.org/2014/tickets/
http://postgresopen.org/2014/callforpapers/

The 4th PgDay Ecuador will be held on Tuesday 7th in October at the
city of Quito, as part of the 5th International Congress of Free
Software.  Send talk proposals to ecpug AT postgresql DOT org.

The sixth PGDay Cubano be held on 13 and 14 October 2014 in Habana.
https://postgresql.uci.cu/?p=380

PGConf.EU 2014 in Madrid, Spain on October 21-24 is now open for
registration.
http://2014.pgconf.eu/registration/

PGDay.IT 2014 will take place in Prato on November the 7th 2014.  The
International Call For Papers is now open:
http://2014.pgday.it/call-for-papers-en/

== 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 david <at> fetter.org, German language
to pwn <at> pgug.de, Italian language to pwn <at> itpug.org.  Spanish language
to pwn <at> arpug.com.ar.

== Applied Patches ==

Fujii Masao pushed:

- Fix documentation oversights about pageinspect and initialization
  fork.  The initialization fork was added in 9.1, but has not been
  taken into consideration in documents of get_raw_page function in
  pageinspect and storage layout. This commit fixes those oversights.
  get_raw_page can read not only a table but also an index, etc. So it
  should be documented that the function can read any relation. This
  commit also fixes the document of pageinspect that way.  Back-patch
  to 9.1 where those oversights existed.  Vik Fearing, review by
  MauMau
  http://git.postgresql.org/pg/commitdiff/7d835ff4db19c515171d6c8de772536c55600753

- Add tab-completion for \unset and valid setting values of psql
  variables.  This commit also changes tab-completion for \set so that
  it displays all the special variables like COMP_KEYWORD_CASE.
  Previously it displayed only variables having the set values. Which
  was not user-friendly for those who want to set the unset variables.
  This commit also changes tab-completion for :variable so that only
  the variables having the set values are displayed. Previously even
  unset variables were displayed.  Pavel Stehule, modified by me.
  http://git.postgresql.org/pg/commitdiff/e15c4ab5fb0de2cab393ed4be2136e1832746412

- Change first call of ProcessConfigFile so as to process only
  data_directory.  When both postgresql.conf and postgresql.auto.conf
  have their own entry of the same parameter, PostgreSQL uses the
  entry in postgresql.auto.conf because it appears last in the
  configuration scan. IOW, the other entries which appear earlier are
  ignored. But, previously, ProcessConfigFile() detected the invalid
  settings of even those unused entries and emitted the error messages
  complaining about them, at postmaster startup. Complaining about the
  entries to ignore is basically useless.  This problem happened
  because ProcessConfigFile() was called twice at postmaster startup
  and the first call read only postgresql.conf.  That is, the first
  call could check the entry which might be ignored eventually by the
  second call which read both postgresql.conf and
  postgresql.auto.conf.  To work around the problem, this commit
  changes ProcessConfigFile so that its first call processes only
  data_directory and the second one does all the entries. It's OK to
  process data_directory in the first call because it's ensured that
  data_directory doesn't exist in postgresql.auto.conf.  Back-patch to
  9.4 where postgresql.auto.conf was added.  Patch by me. Review by
  Amit Kapila
  http://git.postgresql.org/pg/commitdiff/3e3f65973a3c94a699a1659254b89c4f77f0a6a7

- Fix typo in \setrandom document.  Fabien COELHO
  http://git.postgresql.org/pg/commitdiff/d6ded369a7793c926661f492c153a6dd05afc5bc

- Expose -S option in pg_receivexlog.  This option is equivalent to
  --slot option which pg_receivexlog has already supported, which
  specifies the replication slot to use for WAL streaming.
  pg_recvlogical has already supported both options, and this commit
  makes pg_receivexlog consistent with pg_recvlogical regarding the
  slot option.  Back-patch to 9.4 where the slot option was added.
  Michael Paquier
  http://git.postgresql.org/pg/commitdiff/52bffe3499d8e5f61efa385ab3c6a074314ee5db

- Fix help message in pg_ctl.  Previously the help message described
  that -m is an option for "stop", "restart" and "promote" commands in
  pg_ctl. But actually that's not an option for "promote". So this
  commit fixes that incorrect description in the help message.
  Back-patch to 9.3 where the incorrect description was added.
  http://git.postgresql.org/pg/commitdiff/a4287a689d10bd4863e3dfbf9c4f232feeca0cdd

- Add missing index terms for replication commands in the document.
  Previously only CREATE_REPLICATION_SLOT was exposed as an index
  term.  That's odd and there is no reason not to add index terms for
  other replication commands.  Back-patch to 9.4.
  http://git.postgresql.org/pg/commitdiff/3e9f70f1287b9324e398a084a8e881ea6aefc3eb

Tatsuo Ishii pushed:

- Enhance pgbench's option checking.  Now benchmarking options such as
  -c cannot be used if initializing option (-i) is specified.  Also
  initializing options such as -F cannot be used if initializing
  option is not specified.  Tatsuo Ishii and Fabien COELHO.
  http://git.postgresql.org/pg/commitdiff/51222a176624e8529143f26f43da200c5beb0e9e

Andres Freund pushed:

- Be less aggressive in asking for feedback of logical walsender
  clients.  When doing logical decoding using
  START_LOGICAL_REPLICATION in a walsender process the walsender
  sometimes was sending out keepalive messages too frequently. Asking
  for feedback every time.  WalSndWaitForWal() sends out keepalive
  messages when it's waiting for new WAL to be generated locally when
  it sees that the remote side hasn't yet flushed WAL up to the local
  position. That generally is good but causes problems if the remote
  side only writes but doesn't flush changes yet. So check for both
  remote write and flush position.  Additionally we've asked for
  feedback to the keepalive message which isn't warranted when waiting
  for WAL in contrast to preventing timeouts because of
  wal_sender_timeout.  Complaint and patch by Steve Singer.
  http://git.postgresql.org/pg/commitdiff/41d5f8ad734f28ca425636d5ac4c8ea9c29002a5

- pg_recvlogical message and code improvements.  Some error messages
  complained about --init and --stop being used whereas the --create
  and --drop are the correct verbs. Fix that.  Also a XLogRecPtr was
  tested in a boolean fashion instead of being compared to
  InvalidXLogRecPtr.  Backpatch to 9.4 where pg_recvlogical was
  introduced.  Michael Paquier
  http://git.postgresql.org/pg/commitdiff/596385be06e1c8ac7291958a556b10b37ee333d5

Tom Lane pushed:

- Prevent memory leaks in parseRelOptions().  parseRelOptions() tended
  to leak memory in the caller's context.  Most of the time this
  doesn't really matter since the caller's context is at most
  query-lifespan, and the function won't be invoked very many times.
  However, when testing with CLOBBER_CACHE_RECURSIVELY, the same
  relcache entry can get rebuilt a *lot* of times in one query,
  leading to significant intraquery memory bloat if it has any
  reloptions.  Noted while investigating a related report from Tomas
  Vondra.  In passing, get rid of some Asserts that are redundant with
  the one done by deconstruct_array().  As with other patches to avoid
  leaks in CLOBBER_CACHE testing, it doesn't really seem worth
  back-patching this.
  http://git.postgresql.org/pg/commitdiff/a844c29966d7c0cd6a457e9324f175349bb12df0

- Prevent memory leaks in RelationGetIndexList,
  RelationGetIndexAttrBitmap.  When replacing rd_indexlist,
  rd_indexattr, etc, we neglected to pfree any old value of these
  fields.  Under ordinary circumstances, the old value would always be
  NULL, so this seemed reasonable enough.  However, in cases where
  we're rebuilding a system catalog's relcache entry and another cache
  flush occurs on that same catalog meanwhile, it's possible for the
  field to not be NULL when we return to the outer level, because we
  already refilled it while recovering from the inner flush.  This
  leads to a fairly small session-lifespan leak in CacheMemoryContext.
  In real-world usage the leak would be too small to notice; but in
  testing with CLOBBER_CACHE_RECURSIVELY the leakage can add up to the
  point of causing OOM failures, as reported by Tomas Vondra.  The
  issue has been there a long time, but it only seems worth fixing in
  HEAD, like the previous fix in this area (commit 078b2ed291c758e7).
  http://git.postgresql.org/pg/commitdiff/ab8c84db2f7af008151b848cf1d6a4672a39eecd

- Update SysV parameter configuration documentation for FreeBSD.
  FreeBSD hasn't made any use of kern.ipc.semmap since 1.1, and newer
  releases reject attempts to set it altogether; so stop recommending
  that it be adjusted.  Per bug #11161.  Back-patch to all supported
  branches.  Before 9.3, also incorporate commit 7a42dff47, which
  touches the same text and for some reason was not back-patched at
  the time.
  http://git.postgresql.org/pg/commitdiff/5ff5bfb5f0d83a538766903275b230499fa9ebe1

- Fix bogus commutator/negator links for JSONB containment operators.
  < <at>  and  <at> > are each other's commutators, but they were incorrectly
  marked as being each other's negators instead.  (This was actually
  questioned in a comment in the original commit, but nobody followed
  through :-(.) Per bug #11178 from Christian Pronovost.  In passing,
  fix some JSONB operator descriptions that were randomly different
  from the phrasing of every other similar description.  catversion
  bump for pg_catalog contents change.
  http://git.postgresql.org/pg/commitdiff/e3f9c16838358b6b3679dd014455d310919d7efa

- Add opr_sanity queries to inspect commutator/negator links more
  closely.  Make lists of the names of all operators that are claimed
  to be commutator pairs or negator pairs.  This is analogous to the
  existing queries that make lists of all operator names appearing in
  particular opclass strategy slots.  Unexpected additions to these
  lists are likely to be mistakes; had we had these queries in place
  before, bug #11178 might've been prevented.
  http://git.postgresql.org/pg/commitdiff/a068b5b65f83660fc99c3faf39ed50493b010fbb

- Fix bogus return macros in range_overright_internal().
  PG_RETURN_BOOL() should only be used in functions following the V1
  SQL function API.  This coding accidentally fails to fail since
  letting the compiler coerce the Datum representation of bool back to
  plain bool does give the right answer; but that doesn't make it a
  good idea.  Back-patch to older branches just to avoid unnecessary
  code divergence.
  http://git.postgresql.org/pg/commitdiff/737cdc2d1412f3e4115137ca6fa14d1b3c39dcbc

- Improve DISCARD documentation.  The new DISCARD SEQUENCES option was
  inadequately described, and hadn't been mentioned at all in the
  initial Description paragraph.  Rather than rectifying the latter
  the hard way, it seemed better to rewrite the description as a
  summary, instead of having it basically duplicate statements made
  under Parameters.  Be more consistent about the ordering of the
  options, too.
  http://git.postgresql.org/pg/commitdiff/259904ecd42a46f5bb66bb85d547eba5b64a2cfa

- Make an editorial pass over the 9.4 release notes.  Update the notes
  to include commits through today, and do a lot of wordsmithing and
  markup adjustment.  Notably, don't use <link> where <xref> will do;
  since we got rid of the text-format HISTORY file, there is no longer
  a reason to avoid <xref>.
  http://git.postgresql.org/pg/commitdiff/f66faadc4420fdc34f66057f493a0e09c0ad8a58

- Use ISO 8601 format for dates converted to JSON, too.  Commit
  f30015b6d794c15d52abbb3df3a65081fbefb1ed made this happen for
  timestamp and timestamptz, but it seems pretty inconsistent to not
  do it for simple dates as well.  (In passing, I re-pgindent'd
  json.c.)
  http://git.postgresql.org/pg/commitdiff/e56ec50c1622010c010e1c84bc02ce44285c4f41

Peter Eisentraut pushed:

- doc: Remove obsolete set element DSSSL customizations.  We don't use
  set elements (collection of books) anymore, so this is just dead
  code.
  http://git.postgresql.org/pg/commitdiff/faa14acc9b958d7b811d0aa624774f36e3fab750

- Fix whitespace
  http://git.postgresql.org/pg/commitdiff/5333c72c951cd30e46cece18e75bea53f7149b1b

- Add some noreturn attributes based on compiler recommendations
  http://git.postgresql.org/pg/commitdiff/1d678bf7bc66d4478bdee51278946dcc9ae8cae5

- doc: Fix DocBook XML validity.  See
  3a9d430af515e9dd8a9d34a4011367e667a66521.  A new one snuck in.
  http://git.postgresql.org/pg/commitdiff/d34b48a021b181e30c53280d336820740f67570b

- Set shared library path for in-tree TAP tests.  When the TAP tests
  are run in-tree (make check), set the shared library path using the
  appropriate environment variable, using a logic similar to
  pg_regress, so that the right libraries are used.
  http://git.postgresql.org/pg/commitdiff/f669b61476b2efd79701a7a104e9de2fe11e4e42

- Fix whitespace
  http://git.postgresql.org/pg/commitdiff/9ee9ca545bda210fec78381e8ad4ad1e1618b67c

- doc: Work around stylesheet bug for man build.  The upstream
  stylesheets for man output insert a *roff comment for an occurrence
  of an indexterm, for reasons that have apparently been lost in
  history.  This, however, is done incorrectly and causes some
  formatting problems.  This hasn't been an issue until now, but the
  reorganization of indexterm elements inside variablelists has
  triggered this issue.  The upstream fix
  (http://sourceforge.net/p/docbook/bugs/1340/) is to drop indexterms
  altogether in man output, and so we'll do the same here.
  http://git.postgresql.org/pg/commitdiff/1330e2922c7f7d42780109247c28ad50a790f96c

Robert Haas pushed:

- Add sortsupport routines for text.  This provides a small but
  worthwhile speedup when sorting text, at least in cases to which the
  sortsupport machinery applies.  Robert Haas and Peter Geoghegan
  http://git.postgresql.org/pg/commitdiff/b34e37bfefbed1bf9396dde18f308d8b96fd176c

- docs: Add missing period.  Fabien COELHO and Robert Haas
  http://git.postgresql.org/pg/commitdiff/751b7041050b7b19bf3001633740616089973ab3

Heikki Linnakangas pushed:

- Doc fix: New York State's capital is Albany.  The inheritance
  example in the manual implies that the capital of New York is New
  York City, but in reality it's Albany.  George Hartzell
  http://git.postgresql.org/pg/commitdiff/ef153ecc55a8f945d576a1e69a51b91046f24bb1

- Remove remnants of a JENTRY_ISFIRST flag bit.  I removed the flag
  earlier, but missed a few references in jsonb.h.
  http://git.postgresql.org/pg/commitdiff/c07693f0c7cde7d269025fe714a124223a189e71

- Break out OpenSSL-specific code to separate files.  This refactoring
  is in preparation for adding support for other SSL implementations,
  with no user-visible effects. There are now two #defines,
  USE_OPENSSL which is defined when building with OpenSSL, and USE_SSL
  which is defined when building with any SSL implementation.
  Currently, OpenSSL is the only implementation so the two #defines go
  together, but USE_SSL is supposed to be used for
  implementation-independent code.  The libpq SSL code is changed to
  use a custom BIO, which does all the raw I/O, like we've been doing
  in the backend for a long time. That makes it possible to use
  MSG_NOSIGNAL to block SIGPIPE when using SSL, which avoids a couple
  of syscall for each send(). Probably doesn't make much performance
  difference in practice - the SSL encryption is expensive enough to
  mask the effect - but it was a natural result of this refactoring.
  Based on a patch by Martijn van Oosterhout from 2006. Briefly
  reviewed by Alvaro Herrera, Andreas Karlsson, Jeff Janes.
  http://git.postgresql.org/pg/commitdiff/680513ab79c7e12e402a2aad7921b95a25a4bcc8

Bruce Momjian pushed:

- pg_upgrade:  error if run from top of new PGDATA on Windows.  Print
  a clear error message in this case, rather than wait for initdb
  --sync-only to generate a "Permission denied" error.
  http://git.postgresql.org/pg/commitdiff/e4c3c99ac3d4777458ef3e94b037438b244b72b6

- pg_upgrade:  fix define adjusted during testing.  from commit
  e4c3c99ac3d4777458ef3e94b037438b244b72b6
  http://git.postgresql.org/pg/commitdiff/ea9b8abd6f457706a3501849d21587af178113a1

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Michael Paquier sent in three more revisions of a patch to support N
synchronous standby servers, N>1.

Fujii Masao sent in another revision of a patch to allow showing only
failed queries in psql.

Fujii Masao sent in another revision of a patch to ignore unused GUCs
at startup.

Michael Paquier sent in two more revisions of a patch to improve
versioning on Windows.

Michael Paquier sent in another revision of a patch to remove the
dependency on wsock32.lib when compiling code on Windows.

Michael Paquier sent in a patch to fix the tab padding for the new
option -F in the getops switch.

Haribabu Kommi sent in another revision of a patch to fix the fact
that inet types don't support min/max.

Heikki Linnakangas sent in another revision of a patch to add an SSL
regression test suite.

Fabien COELHO sent in a patch to fix some issues in a previous patch
which makes PL/PgSQL throw an error during compilation (instead of
runtime) if the number of parameters passed to RAISE don't match the
number of placeholders in error message.

Sean Chittenden sent in a patch to fix a potential performance
regression due to mmap(2) on FreeBSD.

Fujii Masao sent in another revision of a patch to add
pg_last_xact_insert_timestamp.

Heikki Linnakangas sent in another revision of a patch to make WAL
format and API changes.

Heikki Linnakangas sent in another revision of a patch to support
Windows SChannel as an OpenSSL replacement.

Furuya Osamu sent in two revisions of a patch to add a setting to send
status packets after fsync to --status-interval of pg_receivexlog.

Atri Sharma sent in a WIP patch to enable GROUPING SETS.

Heikki Linnakangas sent in two revisions of a patch to refactor
heapam.c redo routines to use XLogReplayBuffer.

Etsuro Fujita sent in another revision of a patch to compute
attr_needed for child relations.

Dilip Kumar sent in another revision of a patch to allow parallel
cores to be used by vacuumdb.

Fujii Masao sent in a patch to enable WAL archiving even on a standby.

MauMau sent in another revision of a patch to implement pg_copy, a
command for reliable WAL archiving.

David Rowley sent in a patch to change some security-related uses of
strncpy to strlcpy.

Tom Lane an Heikki Linnakangas traded patches to fix an issue where
TOAST fails to compress JSONB fields.

Keith Baker sent in two more revisions of a patch to implement the
locking needed for a QNX 6.5 port.

SAWADA Masahiko sent in another revision of a patch to add line number
as a prompt option to psql.

Fabien COELHO sent in a patch to add a throttling latency limit to
pgbench.

Fujii Masao sent in a patch to change \watch so that it displays how
long the query takes if \timing is enabled.

Fujii Masao sent in a patch to allow immediate standby promotion.

Rukh Meski sent in another revision of a patch to add LIMIT for UPDATE
and DELETE.

Kyotaro HORIGUCHI sent in a patch to add a new GUC category
PGC_BACKEND_USERSET and change local_preload_libraries to use it.

Peter Eisentraut sent in a patch to improve the speed of make
check-world by having it only create one temporary installation, where
before it made a temporary installation for every subdirectory.

Alvaro Herrera and Heikki Linnakangas traded patches to implement
minmax indexes.

Fujii Masao sent in a patch to expose replication commands as index
terms.

Amit Kapila and Michael Paquier traded patches to fix an issue where
the option -T in pg_basebackup doesn't work on Windows.

Marko (johto) Tiikkaja sent in another revision of a patch to add PGP
signatures to the pgcrypto extension.

Marko (johto) Tiikkaja sent in another revision of a patch to add PGP
armor headers to the pgcrypto extension.

Fujii Masao sent in a patch to add a memory barrier to pgstat.

Kaigai Kouhei sent in another revision of a patch to implement the
custom plan API.

Pavel Stehule sent in a patch to fix an issue with pg_dump where the
existence of a large object (lo) could cause an unrestorable dump.

Joachim Wieland sent in a patch to refactor pg_dump to remove global
variables.  In addition to being a good in itself, this is in
preparation for a parallel analog of "pg_dump | psql".

Noah Misch sent in a patch to fix the fact that the sample LDIF for
pg_service.conf no longer works.

Fabien COELHO sent in a patch to add a --tuple-size option to pgbench.

Tomas Vondra sent in another revision of a patch to fix an issue where
bad estimation together with large work_mem generates terrible slow
hash joins.

David Rowley sent in another revision of a patch to support SEMI and
ANTI join removal.

Rahila Syed sent in another revision of a patch to support various
types of compression of full-page writes.

Fabrízio de Royes Mello sent in another revision of a patch to enable
ALTER TABLE ... SET LOGGED.

Stephen Frost sent in two more revisions of a patch to tweak the
command tags in ALTER TABLESPACE MOVE.

Fujii Masao sent in another revision of a patch to add
PENDING_LIST_CLEANUP_SIZE.

Marco Nenciarini sent in a patch to add backup profile to base backup.

Michael Paquier sent in another revision of a patch to add support for
physical slot creation/deletion in pg_receivexlog.

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

Gilles Darold | 11 Aug 16:19 2014

pgBadger v6.0 is out

Paris, France - August 11th, 2014

DALIBO is proud to announce the release of pgBadger 6.0.

pgBadger is a PostgreSQL performance analyzer, built for speed with
fully detailed reports based on your PostgreSQL log files.

This new major release fixes several issues and adds some new features:

  * Automatic cleanup of binary files in incremental mode.
  * Automatic handling of retention with a maximum number of weeks to
    keep reports.
  * Incremental mode improvement by allowing the use of multiprocessing
    with multiple log file.
  * Now reports the query latency percentiles on the general activity
    table (percentiles are 90, 95, 99).
  * A new output format: JSON. This format is good for sharing data with
    other tools.
  * Using the --anonymize option pgBadger will anonymize all literal
    values in the queries.
  * Add a click-to-select button in front of each query that allow to
    just use Ctrl+C to copy it on clipboard.
  * Several space usage improvement in incremental mode, the -X option
    allow the use of external CSS and Javascript files.
  * A new pgBadger logo

Warning: the behavior of pgBadger in incremental mode has changed. It
will now always cleanup the output directory of all the obsolete binary
file. If you were using those files to build your own reports, you can
prevent pgBadger to remove them by using the --noclean option. Note that
if you use the retention feature, all those files in obsolete
directories will be removed too.

For the complete list of changes, please checkout the release note on
https://github.com/dalibo/pgbadger/blob/master/ChangeLog

===== Links & Credits =====

DALIBO would like to thank the developers who submitted patches and the
users who reported bugs and feature requests, especially Herve Werner,
Julien Rouhaud, Josh Berkus, CZAirwolf, Bruno Almeida, Marc Cousin,
Thomas Reiss, Rodolphe Quiedeville, Himanchali, Guilhem Rambal, Shanzhang
Lan, Xavier Millies-Lacroix, Kong Man, wmorancfi, flopma and birkosan.

pgBadger is an open project. Any contribution to build a better tool is
welcome. You just have to send your ideas, features requests or patches
using the GitHub tools or directly on our mailing list.

Links :

  * Download : http://dalibo.github.io/pgbadger/
  * Mailing List : https://listes.dalibo.com/cgi-bin/mailman/listinfo/pgbagder

--------------

**About pgBadger** :

pgBagder is a new generation log analyzer for PostgreSQL, created by
Gilles Darold (also author of ora2pg, the powerful migration tool).
pgBadger is a fast and easy tool to analyze your SQL traffic and create
HTML5 reports with dynamics graphs. pgBadger is the perfect tool to
understand the behavior of your PostgreSQL servers and identify which
SQL queries need to be optimized.

Docs, Download & Demo at http://dalibo.github.io/pgbadger/

--------------

**About DALIBO** :

DALIBO is the leading PostgreSQL company in France, providing support,
trainings and consulting to its customers since 2005. The company
contributes to the PostgreSQL community in various ways, including :
code, articles, translations, free conferences and workshops

Check out DALIBO's open source projects at http://dalibo.github.io

-- 
Gilles Darold
http://dalibo.com - http://dalibo.org

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

David Fetter | 11 Aug 01:35 2014

== PostgreSQL Weekly News - August 10 2014 ==

== PostgreSQL Weekly News - August 10 2014 ==

PGDay Campinas 2014 will take place in Campinas on September 10th.
Sign-up and Lightning Talk submissions are open.
http://pgdaycampinas.com.br/

== PostgreSQL Jobs for August ==

http://archives.postgresql.org/pgsql-jobs/2014-08/threads.php

== PostgreSQL Local ==

PgDay Portland, Oregon 2014 will be held Saturday September 6, 2014.
https://wiki.postgresql.org/wiki/PDXPUGDay2014

Postgres Open 2014 will be in Chicago, IL, USA, September 17-19.
Tickets and Tutorials now available for purchase.
https://postgresopen.org/2014/tickets/
http://postgresopen.org/2014/callforpapers/

The 4th PgDay Ecuador will be held on Tuesday 7th in October at the
city of Quito, as part of the 5th International Congress of Free
Software.  Send talk proposals to ecpug AT postgresql DOT org.

The sixth PGDay Cubano be held on 13 and 14 October 2014 in Habana.
https://postgresql.uci.cu/?p=380

PGConf.EU 2014 in Madrid, Spain on October 21-24 is now open for
registration.
http://2014.pgconf.eu/registration/

PGDay.IT 2014 will take place in Prato on November the 7th 2014.  The
International Call For Papers is now open:
http://2014.pgday.it/call-for-papers-en/

== 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 david <at> fetter.org, German language
to pwn <at> pgug.de, Italian language to pwn <at> itpug.org.  Spanish language
to pwn <at> arpug.com.ar.

== Applied Patches ==

Heikki Linnakangas pushed:

- Windows doesn't have M_PI; define it ourselves when needed.  This
  should fix the Windows build, broken by commit ed802e7d.
  http://git.postgresql.org/pg/commitdiff/cd74a151b5a2498f0909074ebc9e8d8fbe6915b1

- Improve comment.  Based on the old comment, it took me a while to
  figure out what the problem was. The importnat detail is that
  SSL_read() can return WANT_READ even though some raw data was
  received from the socket.
  http://git.postgresql.org/pg/commitdiff/ec903d20e3b4c1a543dbf057055e4ddbfad4d59e

Bruce Momjian pushed:

- pg_upgrade:  remove reference to autovacuum_multixact_freeze_max_age.
  autovacuum_multixact_freeze_max_age was added as a pg_ctl start
  parameter in 9.3.X to prevent autovacuum from running.  However,
  only some 9.3.X releases have autovacuum_multixact_freeze_max_age as
  it was added in a minor PG 9.3 release.  It also isn't needed
  because -b turns off autovacuum in 9.1+.  Without this fix, trying
  to upgrade from an early 9.3 release to 9.4 would fail.  Report by
  EDB Backpatch through 9.3
  http://git.postgresql.org/pg/commitdiff/b4bd6f6b054f62a4ed70065b7b3fa95c012ae89a

- pg_upgrade:  assume user is install user.  The user specified to the
  upgrade was effectively the install user, but that was not clearly
  stated in the comments, documentation, or error messages.
  http://git.postgresql.org/pg/commitdiff/ee646df59ae76d14f76e6fd305c1f9f2eeafd682

- pg_upgrade: prevent oid conflicts with new-cluster TOAST tables.
  Previously, TOAST tables only required in the new cluster could
  cause oid conflicts if they were auto-numbered and a later
  conflicting oid had to be assigned.  Backpatch through 9.3
  http://git.postgresql.org/pg/commitdiff/4c6780fd17aa43ed6362aa682499cc2f9712cc8b

Robert Haas pushed:

- Improve some JSON error messages.  These messages are new in 9.4,
  which hasn't been released yet, so back-patch to REL9_4_STABLE.
  Daniele Varrazzo
  http://git.postgresql.org/pg/commitdiff/0ef99bdce3a6cd3195d7df12093042c16328c71c

- Fix alternate regression test output file.  Commit
  0ef99bdce3a6cd3195d7df12093042c16328c71c broke this.  Jeff Janes
  http://git.postgresql.org/pg/commitdiff/873de34b710196d1e3ce593bd85fa24768e58d6b

- Don't require sort support functions to provide a comparator.  This
  could be useful for datatypes like text, where we might want to
  optimize for some collations but not others.  However, this patch
  doesn't introduce any new sortsupport functions that work this way;
  it merely revises the code so that future patches may do so.  Patch
  by me.  Review by Peter Geoghegan.
  http://git.postgresql.org/pg/commitdiff/1d41739e5a04b0e93304d24d864b6bfa3efc45f2

- Add PG_RETURN_UINT16 macro.  Manuel Kniep
  http://git.postgresql.org/pg/commitdiff/73cfa37afe3243c0ccdc6ae72cfcc53a37761521

Kevin Grittner pushed:

- Fix typo in C comment.
  http://git.postgresql.org/pg/commitdiff/49d1e03d64f36a345c92901c4d13bf683f99eeec

Fujii Masao pushed:

- Change ParseConfigFp() so that it doesn't process unused entry of
  each parameter.  When more than one setting entries of same
  parameter exist in the configuration file, PostgreSQL uses only
  entry appearing last in configuration file scan. Since the other
  entries are not used, ParseConfigFp() doesn't need to process them,
  but previously it did that. This problematic behavior caused the
  configuration file scan to detect invalid settings of unused entries
  (e.g., existence of multiple entries of PGC_POSTMASTER parameter)
  and log the messages complaining about them.  This commit changes
  the configuration file scan so that it processes only last entry of
  each parameter.  Note that when multiple entries of same parameter
  exist both in postgresql.conf and postgresql.auto.conf, unused
  entries in postgresql.conf are still processed only at postmaster
  startup.  The problem has existed since old version, but a user is
  more likely to encounter it since 9.4 where ALTER SYSTEM command was
  introduced.  So back-patch to 9.4.  Amit Kapila, slightly modified
  by me. Per report from Christoph Berg.
  http://git.postgresql.org/pg/commitdiff/e3da0d4d1a47e2049ae16aa30bb7bf3105dc8c45

- Refactor pg_receivexlog main loop code, for readability, take 2.
  Previously the source codes for processing the received data and
  handling the end of stream were included in pg_receivexlog main
  loop. This commit splits out them as separate functions. This is
  useful for improving the readability of main loop code and making
  the future pg_receivexlog-related patch simpler.
  http://git.postgresql.org/pg/commitdiff/6805e02c66eac3857ef1a3d6cfd1ffeea64d9447

- Add -F option to pg_receivexlog, for specifying fsync interval.
  This allows us to specify the maximum time to issue fsync to ensure
  the received WAL file is safely flushed to disk. Without this,
  pg_receivexlog always flushes WAL file only when it's closed and
  which can cause WAL data to be lost at the event of a crash.  Furuya
  Osamu, heavily modified by me.
  http://git.postgresql.org/pg/commitdiff/3dad73e71f08abd86564d5090a58ca71740e07e0

Tom Lane pushed:

- Fix typo in docs.  s/XIDs XIDs/XIDs/ in one place in
  maintenance.sgml.  Guillaume Lelarge
  http://git.postgresql.org/pg/commitdiff/1add956ac70384a99ed6606e2963a5a53f567add

- Reject duplicate column names in foreign key referenced-columns
  lists.  Such cases are disallowed by the SQL spec, and even if we
  wanted to allow them, the semantics seem ambiguous: how should the
  FK columns be matched up with the columns of a unique index?  (The
  matching could be significant in the presence of opclasses with
  different notions of equality, so this issue isn't just academic.)
  However, our code did not previously reject such cases, but instead
  would either fail to match to any unique index, or generate a
  bizarre opclass-lookup error because of sloppy thinking in the
  index-matching code.  David Rowley
  http://git.postgresql.org/pg/commitdiff/9da86753735ab89b0ee685aea985b25c4218ca0b

- Further cleanup of JSON-specific error messages.  Fix an obvious
  typo in json_build_object()'s complaint about invalid number of
  arguments, and make the errhint a bit more sensible too.  Per
  discussion about how to word the improved hint, change the few
  places in the documentation that refer to JSON object field names as
  "names" to say "keys" instead, since that's what we've said in the
  vast majority of places in the docs.  Arguably "name" is more
  correct, since that's the terminology used in RFC 7159; but we're
  stuck with "key" in view of the naming of json_object_keys() so
  let's at least be self-consistent.  I adjusted a few code comments
  to match this as well, and failed to resist the temptation to clean
  up some odd whitespace choices in the same area, as well as a
  useless duplicate PG_ARGISNULL() check.  There's still quite a bit
  of code that uses the phrase "field name" in non-user- visible ways,
  so I left those usages alone.
  http://git.postgresql.org/pg/commitdiff/495cadda5ed55f63db9a91d174b6fad0e1816204

- Clean up handling of unknown-type inputs in json_build_object and
  friends.  There's actually no need for any special case for
  unknown-type literals, since we only need to push the value through
  its output function and unknownout() works fine.  The code that was
  here was completely bizarre anyway, and would fail outright in cases
  that should work, not to mention suffering from some copy-and-paste
  bugs.
  http://git.postgresql.org/pg/commitdiff/92f57c9ae95668636bc77d3cda3edbdfd83320d9

- Clarify type resolution behavior for domain types.  The user
  documentation was vague and not entirely accurate about how we treat
  domain inputs for ambiguous operators/functions.  Clarify that, and
  add an example and some commentary.  Per a recent question from Adam
  Mackler.  It's acted like this ever since we added domains, so
  back-patch to all supported branches.
  http://git.postgresql.org/pg/commitdiff/6aa61580e08d58909b2a8845a4087b7699335ee0

Peter Eisentraut pushed:

- Small message fixes
  http://git.postgresql.org/pg/commitdiff/f25e0bf5e0af01a687395a76e676dadeb4a60d0a

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Dilip Kumar sent in another revision of a patch to allow parallel
cores to be used by vacuumdb.

Etsuro Fujita sent in another revision of a patch to optimize writes
to foreign tables using the PostgreSQL FDW.

Alexander Korotkov sent in another revision of a patch to add KNN-GiST
with recheck.

Heikki Linnakangas sent in a patch to create an SSL regression test
suite.

Fabien COELHO sent in two more revisions of a patch to add modulo to
pgbench.

Jeff Davis sent in two more revisions of a patch to implement better
memory accounting, infrastructure for a memory-bounded HashAgg.

Fujii Masao sent in a patch to add PGC_SU_BACKEND.

Jeff Janes sent in a patch to fix one of the regression tests changed
by another patch which fixed redundant i18n strings in json.

Fujii Masao sent in two more revisions of a patch to add a
synchrounous mode to pg_receivexlog.

Robert Haas and Peter Geoghegan traded patches to add an optional
comparator for B-Tree sort support.

David Rowley sent in two more revisions of a patch to allow certain
SEMI and ANTI join removals.

Alvaro Herrera and Heikki Linnakangas traded patches to implement
minmax indexes.

Marko (johto) Tiikkaja sent in another revision of a patch to add
plpgsql.extra_warnings='num_into_expressions'.

Marko (johto) Tiikkaja sent in two revisions of a patch to enable PGP
signatures in the pgcrypto extenstion.

Tatsuo Ishii and Fabien COELHO started patching pgbench to ensure that
its parameters are checked better.

Etsuro Fujita sent in two revisions of a patch to compute attr_needed
for child rels.  As there were already two different places this
functionality was used, this patch factored out the functionality in
order to add a third use case, namely allowing foreign tables to be in
table inheritance hierarchies.

Heikki Linnakangas sent in another revision of a patch to Invent a new
internal API for interfacing with SSLv3.

Fujii Masao sent in a patch to enable specifying the unit in storage
parameters.

Pavel Stehule and Fujii Masao traded patches to allow tab completion
for \pset variables in psql.

Marko (johto) Tiikkaja sent in a patch to add PGP armor headers in the
pgcrypto extension.

MauMau sent in another revision of a patch to fix an unconditional
truncation that should have been a conditional truncation for
temporary relations.

Fujii Masao sent in a patch to add a new GIN index storage parameter
"PENDING_LIST_CLEANUP_SIZE" which specifies the maximum size of GIN
pending list.

Michael Paquier sent in a patch to add support for N synchronous
standby servers for N > 1.

Jeff Davis sent in a patch to enable memory-bounded HashAgg.

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

David Fetter | 4 Aug 07:36 2014

== PostgreSQL Weekly News - August 03 2014 ==

== PostgreSQL Weekly News - August 03 2014 ==

PGDay.IT 2014 will take place in Prato on November the 7th 2014.
The deadline of the International Call For Papers was postponed until
9 August, 2014:
http://2014.pgday.it/call-for-papers-en/

== PostgreSQL Jobs for August ==

http://archives.postgresql.org/pgsql-jobs/2014-08/threads.php

== PostgreSQL Local ==

PgDay Portland, Oregon 2014 will be held Saturday September 6, 2014.
https://wiki.postgresql.org/wiki/PDXPUGDay2014

Postgres Open 2014 will be in Chicago, IL, USA, September 17-19.
Tickets and Tutorials now available for purchase.
https://postgresopen.org/2014/tickets/
http://postgresopen.org/2014/callforpapers/

The 4th PgDay Ecuador will be held on Tuesday 7th in October at the
city of Quito, as part of the 5th International Congress of Free
Software.  Send talk proposals to ecpug AT postgresql DOT org.

The sixth PGDay Cubano be held on 13 and 14 October 2014 in Habana.
https://postgresql.uci.cu/?p=380

PGConf.EU 2014 in Madrid, Spain on October 21-24 is now open for
registration.
http://2014.pgconf.eu/registration/

PGDay.IT 2014 will take place in Prato on November the 7th 2014.  The
International Call For Papers is now open:
http://2014.pgday.it/call-for-papers-en/

== 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 david <at> fetter.org, German language
to pwn <at> pgug.de, Italian language to pwn <at> itpug.org.  Spanish language
to pwn <at> arpug.com.ar.

== Applied Patches ==

Tom Lane pushed:

- Fix obsolete statement in smgr/README.  Since commit
  2d00190495b22e0d0ba351b2cda9c95fb2e3d083, fork numbers are defined
  in relpath.h not relfilenode.h.  Fabrízio de Royes Mello
  http://git.postgresql.org/pg/commitdiff/248fc1f10716964b7e7d0f8ada686801d1e36445

- Avoid wholesale autovacuuming when autovacuum is nominally off.
  When autovacuum is nominally off, we will still launch autovac
  workers to vacuum tables that are at risk of XID wraparound.  But
  after we'd done that, an autovac worker would proceed to autovacuum
  every table in the targeted database, if they meet the usual
  thresholds for autovacuuming.  This is at best pretty unexpected; at
  worst it delays response to the wraparound threat.  Fix it so that
  if autovacuum is nominally off, we *only* do forced vacuums and not
  any other work.  Per gripe from Andrey Zhidenkov.  This has been
  like this all along, so back-patch to all supported branches.
  http://git.postgresql.org/pg/commitdiff/f51ead09df19f0a074c07657b7de8dba0f3050d6

Fujii Masao pushed:

- Reword the sentence for pg_logical_slot_peek_changes function.
  Previously the duplicated paragraphs were used next to each other in
  the document to demonstrate that the changes in the stream were not
  consumed by pg_logical_slot_peek_changes function.  But some users
  misunderstood that the duplication of the same paragraph was just
  typo. So this commit rewords the sentence in the latter paragraph
  for less confusing.  Christoph Moench-Tegeder
  http://git.postgresql.org/pg/commitdiff/61e48efba579682f75332688bdb89f9eee24fb63

- Fix bug in pg_receivexlog --verbose.  In 9.2, pg_receivexlog with
  verbose option has emitted the messages at the end of each WAL file.
  But the commit 0b63291 suppressed such messages by mistake. This
  commit fixes the bug so that pg_receivexlog --verbose outputs such
  messages again.  Back-patch to 9.3 where the bug was added.
  http://git.postgresql.org/pg/commitdiff/694fd33e23170f64d30ef35e647b824d34938e09

- Add missing PQclear() calls into pg_receivexlog.  Back-patch to 9.3.
  http://git.postgresql.org/pg/commitdiff/b819dd7cb55aed1d607cef36b0ecd1a0642872b2

Heikki Linnakangas pushed:

- Oops, fix recoveryStopsBefore functions for regular commits.
  Pointed out by Tom Lane. Backpatch to 9.4, the code was structured
  differently in earlier branches and didn't have this mistake.
  http://git.postgresql.org/pg/commitdiff/60d931827b0c37fbce74d04e45d0220d57ddd06a

- Treat 2PC commit/abort the same as regular xacts in recovery.  There
  were several oversights in recovery code where COMMIT/ABORT PREPARED
  records were ignored: pg_last_xact_replay_timestamp() (wasn't
  updated for 2PC commits), recovery_min_apply_delay (2PC commits were
  applied immediately), recovery_target_xid (recovery would not stop
  if the XID used 2PC) The first of those was reported by Sergiy Zuban
  in bug #11032, analyzed by Tom Lane and Andres Freund. The bug was
  always there, but was masked before commit
  d19bd29f07aef9e508ff047d128a4046cc8bc1e2, because COMMIT PREPARED
  always created an extra regular transaction that was WAL-logged.
  Backpatch to all supported versions (older versions didn't have all
  the features and therefore didn't have all of the above bugs).
  http://git.postgresql.org/pg/commitdiff/e74e0906fad5fcdcc807d4655cdc69dded5d58f2

- Move log_newpage and log_newpage_buffer to xlog.c.  log_newpage is
  used by many indexams, in addition to heap, but for historical
  reasons it's always been part of the heapam rmgr. Starting with 9.3,
  we have another WAL record type for logging an image of a page,
  XLOG_FPI. Simplify things by moving log_newpage and
  log_newpage_buffer to xlog.c, and switch to using the XLOG_FPI
  record type.  Bump the WAL version number because the code to replay
  the old HEAP_NEWPAGE records is removed.
  http://git.postgresql.org/pg/commitdiff/54685338e37889eebd473804c3feb006dd83a882

- Fix typo in user manual
  http://git.postgresql.org/pg/commitdiff/822ff44c822007ee14cacfebfe0792d1de669df9

Alvaro Herrera pushed:

- Simplify multixact freezing a bit.  Testing for abortedness of a
  multixact member that's being frozen is unnecessary: we only need to
  know whether the transaction is still in progress or committed to
  determine whether it must be kept or not.  This let us simplify the
  code a bit and avoid a useless TransactionIdDidAbort test.
  Suggested by Andres Freund awhile back.
  http://git.postgresql.org/pg/commitdiff/c2581794f37e76c910eb91f1bf1f1e581123abd6

- Avoid uselessly looking up old LOCK_ONLY multixacts.  Commit
  0ac5ad5134f2 removed an optimization in multixact.c that skipped
  fetching members of MultiXactId that were older than our
  OldestVisibleMXactId value.  The reason this was removed is that it
  is possible for multixacts that contain updates to be older than
  that value.  However, if the caller is certain that the multi does
  not contain an update (because the infomask bits say so), it can
  pass this info down to GetMultiXactIdMembers, enabling it to use the
  old optimization.  Pointed out by Andres Freund in
  20131121200517.GM7240 <at> alap2.anarazel.de
  http://git.postgresql.org/pg/commitdiff/05315498012530d44cd89a209242a243374e274d

Bruce Momjian pushed:

- pg_upgrade:  improve C comment wording
  http://git.postgresql.org/pg/commitdiff/d826d8ecce80e318220a8a4e3d989a38397e5689

Peter Eisentraut pushed:

- doc: Clean up some recently added PL/pgSQL documentation Capitalize
  titles consistently.  Fix some grammar.  Group "Obtaining
  Information About an Error" under "Trapping Errors", but make
  "Obtaining the Call Stack Context Information" its own section,
  since it's not about errors.
  http://git.postgresql.org/pg/commitdiff/232f1475dce23e2fdd0568b35e9a7c470ae6c8ae

Robert Haas pushed:

- Fix mishandling of background worker PGPROCs in EXEC_BACKEND builds.
  InitProcess() relies on IsBackgroundWorker to decide whether the
  PGPROC for a new backend should be taken from ProcGlobal's freeProcs
  or from bgworkerFreeProcs.  In EXEC_BACKEND builds, InitProcess() is
  called sooner than in non-EXEC_BACKEND builds, and
  IsBackgroundWorker wasn't getting initialized soon enough.  Report
  by Noah Misch.  Diagnosis and fix by me.
  http://git.postgresql.org/pg/commitdiff/e280c630a87e1b8325770c6073097d109d79a00f

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Laurenz Albe sent in a patch to make pg_dump behave consistently for
different archive formats.

MauMau and Andres Freund traded patches to fix an issue with sinval.

Thomas Munro sent in three more revisions of a patch to add SKIP
LOCKED DATA.

Furuya Osamu sent in another revision of a patch to add an synchronous
mode to pg_receivexlog.

Keith Baker sent in a patch to add a QNX 6.5 port.

Fabien COELHO sent in two more revisions of a patch to fix some issues
in the Gaussian distribution patch for pgbench.

Daniele Varrazzo sent in two revisions of a patch to fix redundant
i18n strings in json.

Heikki Linnakangas sent in a patch to move log_newpage out of
heapam.c.

Kyotaro HORIGUCHI sent in a patch to introduce coarse-grained
parallelism via the postgres_fdw.

Vik Fearing sent in a patch to make the REINDEX syntax more useful.

Heikki Linnakangas sent in another revision of a patch to make WAL
format and API changes.

Anastasia Lubennikova sent in another revision of a patch to add
index-only scans for GiST.

Heikki Linnakangas sent in another revision of a patch to support
Windows SChannel as an OpenSSL replacement.

Fabien COELHO sent in a patch to add the modulo (%) operator to
pgbench.

David Rowley sent in a patch to fix the Windows build.

Peter Geoghegan sent in two more revisions of a patch to add a B-Tree
support function which abbreviates certain searches.

Jeff Davis sent in a patch to explicitly track allocated memory (the
blocks, not the chunks) for each memory context, as well as its
children.

Emre Hasegeli sent in another revision of a patch to enable KNN-GiST
with recheck.

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

David Fetter | 28 Jul 07:41 2014

== PostgreSQL Weekly News - July 27 2014 ==

== PostgreSQL Weekly News - July 27 2014 ==

PostgreSQL 9.4 Beta 2 released.  TEST!
http://www.postgresql.org/about/news/1533/

PostgreSQL bug fix versions 9.3.5, 9.2.9, 9.1.14, 9.0.18, and 8.4.22
out now; 8.4 is now EOL.
Upgrade ASAP!
http://www.postgresql.org/about/news/1534/

== PostgreSQL Product News ==

Bi-Direction Replication (BDR), an asynchronous multi-master
replication system for PostgreSQL, has been announced by 2ndQuadrant.
http://www.2ndQuadrant.com/bdr

pgAdmin3 v1.20.0 Beta 1, a multi-platform stand-alone GUI
administration tool, released.
http://www.pgadmin.org/development/changelog.php

== PostgreSQL Jobs for July ==

http://archives.postgresql.org/pgsql-jobs/2014-07/threads.php

== PostgreSQL Local ==

PgDay Portland, Oregon 2014 will be held Saturday September 6, 2014.
https://wiki.postgresql.org/wiki/PDXPUGDay2014

Postgres Open 2014 will be in Chicago, IL, USA, September 17-19.
Tickets and Tutorials now available for purchase.
https://postgresopen.org/2014/tickets/
http://postgresopen.org/2014/callforpapers/

The 4th PgDay Ecuador will be held on Tuesday 7th in October at the
city of Quito, as part of the 5th International Congress of Free
Software.  Send talk proposals to ecpug AT postgresql DOT org.

The sixth PGDay Cubano be held on 13 and 14 October 2014 in Habana.
https://postgresql.uci.cu/?p=380

PGConf.EU 2014 in Madrid, Spain on October 21-24 is now open for
registration.
http://2014.pgconf.eu/registration/

PGDay.IT 2014 will take place in Prato on November the 7th 2014.  The
International Call For Papers is now open:
http://2014.pgday.it/call-for-papers-en/

== 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 david <at> fetter.org, German language
to pwn <at> pgug.de, Italian language to pwn <at> itpug.org.  Spanish language
to pwn <at> arpug.com.ar.

== Applied Patches ==

Peter Eisentraut pushed:

- Translation updates
  http://git.postgresql.org/pg/commitdiff/cac0d5193bd56dd6ffb70b9fb5a959eedeca01d3

- Update SQL features list
  http://git.postgresql.org/pg/commitdiff/0e819c5e98243b95f622406ab5377422758bbd1a

- gitattributes: Ignore time zone data files for whitespace checks.
  The latest update introduced some funny whitespace, but since they
  are externally maintained files, we add them to the list of files to
  ignore.
  http://git.postgresql.org/pg/commitdiff/8195e9e9c12baea983cb2aab018cda864fa2e223

- Unset some local environment variables in TAP tests.  Unset
  environment variables that control message language, so that we can
  compare some program output with expected strings.  This is very
  similar to what pg_regress does.
  http://git.postgresql.org/pg/commitdiff/24e786f056c0bf009815813de1d7f58ee09f554e

- Fix TAP installcheck tests when current directory name contains
  spaces.  This fixes the installcheck part.  The check part has
  additional problems that will be addressed in a separate commit.
  http://git.postgresql.org/pg/commitdiff/455044d55a89d16d888f289aeaf1229a04a04b9f

- doc: Fix up ALTER TABLESPACE reference page.  The documentation of
  ALTER TABLESPACE ... MOVE was added without any markup, not even
  paragraph breaks.  Fix that, and clarify the text in a few places.
  http://git.postgresql.org/pg/commitdiff/b0d3636c1775524c5c480510aa528ed2e9b50536

Magnus Hagander pushed:

- Properly use DEFAULT_EVENT_SOURCE in pgevent.c.  This was broken and
  reverted in a previous commit. The (this time verified) fix is to
  simly add postgres_fe.h.  MauMau, review by Amit Kapila
  http://git.postgresql.org/pg/commitdiff/4c3c911d26b3944946f8d9b03dbead3ccdf73b19

Tom Lane pushed:

- Defend against bad relfrozenxid/relminmxid/datfrozenxid/datminmxid
  values.  In commit a61daa14d56867e90dc011bbba52ef771cea6770, we
  fixed pg_upgrade so that it would install sane relminmxid and
  datminmxid values, but that does not cure the problem for
  installations that were already pg_upgraded to 9.3; they'll
  initially have "1" in those fields.  This is not a big problem so
  long as 1 is "in the past" compared to the current nextMultiXact
  counter.  But if an installation were more than halfway to the MXID
  wrap point at the time of upgrade, 1 would appear to be "in the
  future" and that would effectively disable tracking of oldest MXIDs
  in those tables/databases, until such time as the counter wrapped
  around.  While in itself this isn't worse than the situation
  pre-9.3, where we did not manage MXID wraparound risk at all, the
  consequences of premature truncation of pg_multixact are worse now;
  so we ought to make some effort to cope with this.  We discussed
  advising users to fix the tracking values manually, but that seems
  both very tedious and very error-prone.  Instead, this patch adopts
  two amelioration rules.  First, a relminmxid value that is "in the
  future" is allowed to be overwritten with a full-table VACUUM's
  actual freeze cutoff, ignoring the normal rule that relminmxid
  should never go backwards.  (This essentially assumes that we have
  enough defenses in place that wraparound can never occur anymore,
  and thus that a value "in the future" must be corrupt.)  Second, if
  we see any "in the future" values then we refrain from truncating
  pg_clog and pg_multixact.  This prevents loss of clog data until we
  have cleaned up all the broken tracking data.  In the worst case
  that could result in considerable clog bloat, but in practice we
  expect that relfrozenxid-driven freezing will happen soon enough to
  fix the problem before clog bloat becomes intolerable.  (Users could
  do manual VACUUM FREEZEs if not.) Note that this mechanism cannot
  save us if there are already-wrapped or already-truncated-away MXIDs
  in the table; it's only capable of dealing with corrupt tracking
  values.  But that's the situation we have with the pg_upgrade bug.
  For consistency, apply the same rules to relfrozenxid/datfrozenxid.
  There are not known mechanisms for these to get messed up, but if
  they were, the same tactics seem appropriate for fixing them.
  http://git.postgresql.org/pg/commitdiff/78db307bb238f4d2d27e62c06a246e88b92fa53b

- Adjust cutoff points in newly-added sanity tests.  Per
  recommendation from Andres Freund.
  http://git.postgresql.org/pg/commitdiff/87f830e0ce03063fc7f856c95fa75a719b3a8ad0

- Release notes for 9.3.5, 9.2.9, 9.1.14, 9.0.18, 8.4.22.
  http://git.postgresql.org/pg/commitdiff/212825f8139abbcfe366a8f884193b5b693921de

- Reject out-of-range numeric timezone specifications.  In commit
  631dc390f49909a5c8ebd6002cfb2bcee5415a9d, we started to handle
  simple numeric timezone offsets via the zic library instead of the
  old CTimeZone/HasCTZSet kluge.  However, we overlooked the fact that
  the zic code will reject UTC offsets exceeding a week (which seems a
  bit arbitrary, but not because it's too tight ...).  This led to
  possibly setting session_timezone to NULL, which results in crashes
  in most timezone-related operations as of 9.4, and crashes in a
  small number of places even before that.  So check for NULL return
  from pg_tzset_offset() and report an appropriate error message.  Per
  bug #11014 from Duncan Gillis.  Back-patch to all supported
  branches, like the previous patch.  (Unfortunately, as of today that
  no longer includes 8.4.)
  http://git.postgresql.org/pg/commitdiff/6412f3e2d09b562fafc129c134e7336c4fe790ed

- Check block number against the correct fork in get_raw_page().
  get_raw_page tried to validate the supplied block number against
  RelationGetNumberOfBlocks(), which of course is only right when
  accessing the main fork.  In most cases, the main fork is longer
  than the others, so that the check was too weak (allowing a
  lower-level error to be reported, but no real harm to be done).
  However, very small tables could have an FSM larger than their heap,
  in which case the mistake prevented access to some FSM pages.  Per
  report from Torsten Foertsch.  In passing, make the bad-block-number
  error into an ereport not elog (since it's certainly not an internal
  error); and fix sloppily maintained comment for
  RelationGetNumberOfBlocksInFork.  This has been wrong since we
  invented relation forks, so back-patch to all supported branches.
  http://git.postgresql.org/pg/commitdiff/27cef0a56111a7a44e0d9b9a7819f7e9f4980a77

- Re-enable error for "SELECT ... OFFSET -1".  The executor has thrown
  errors for negative OFFSET values since 8.4 (see commit
  bfce56eea45b1369b7bb2150a150d1ac109f5073), but in a moment of brain
  fade I taught the planner that OFFSET with a constant negative value
  was a no-op (commit 1a1832eb085e5bca198735e5d0e766a3cb61b8fc).
  Reinstate the former behavior by only discarding OFFSET with a value
  of exactly 0.  In passing, adjust a planner comment that referenced
  the ancient behavior.  Back-patch to 9.3 where the mistake was
  introduced.
  http://git.postgresql.org/pg/commitdiff/27048980f503da22dcd289ec8342b7021c8e73e6

- Rearrange documentation paragraph describing pg_relation_size().
  Break the list of available options into an <itemizedlist> instead
  of inline sentences.  This is mostly motivated by wanting to ensure
  that the cross-references to the FSM and VM docs don't cross page
  boundaries in PDF format; but it seems to me to read more easily
  this way anyway.  I took the liberty of editorializing a bit further
  while at it.  Per complaint from Magnus about 9.0.18 docs not
  building in A4 format.  Patch all active branches so we don't get
  blind-sided by this particular issue again in future.
  http://git.postgresql.org/pg/commitdiff/4fd9e6ffdd9aae51a935c255cbf7691c369ded1b

- Fix a performance problem in pg_dump's dump order selection logic.
  findDependencyLoops() was not bright about cases where there are
  multiple dependency paths between the same two dumpable objects.  In
  most scenarios this did not hurt us too badly; but since the
  introduction of section boundary pseudo-objects in commit
  a1ef01fe163b304760088e3e30eb22036910a495, it was possible for this
  code to take unreasonable amounts of time (tens of seconds on a
  database with a couple thousand objects), as reported in bug #11033
  from Joe Van Dyk.  Joe's particular problem scenario involved
  "pg_dump -a" mode with long chains of foreign key constraints, but I
  think that similar problems could arise with other situations as
  long as there were enough objects.  To fix, add a flag array that
  lets us notice when we arrive at the same object again while
  searching from a given start object.  This simple change seems to be
  enough to eliminate the performance problem.  Back-patch to 9.1,
  like the patch that introduced section boundary objects.
  http://git.postgresql.org/pg/commitdiff/c8e2e0e7129276440d1806dfe4f930c7177ccaac

Noah Misch pushed:

- Diagnose incompatible OpenLDAP versions during build and test.  With
  OpenLDAP versions 2.4.24 through 2.4.31, inclusive, PostgreSQL
  backends can crash at exit.  Raise a warning during "configure"
  based on the compile-time OpenLDAP version number, and test the
  crash scenario in the dblink test suite.  Back-patch to 9.0 (all
  supported versions).
  http://git.postgresql.org/pg/commitdiff/d7cdf6ee36adeac9233678fb8f2a112e6678a770

- MSVC: Substitute $(top_builddir) in REGRESS_OPTS.  Commit
  d7cdf6ee36adeac9233678fb8f2a112e6678a770 introduced a usage thereof.
  Back-patch to 9.0, like that commit.
  http://git.postgresql.org/pg/commitdiff/31f9bbf05928ed8f20b1c371df8098d8c7dddb37

- Report success when Windows kill() emulation signals an exiting
  process.  This is consistent with the POSIX verdict that kill()
  shall not report ESRCH for a zombie process.  Back-patch to 9.0 (all
  supported versions).  Test code from commit
  d7cdf6ee36adeac9233678fb8f2a112e6678a770 depends on it, and log
  messages about kill() reporting "Invalid argument" will cease to
  appear for this not-unexpected condition.
  http://git.postgresql.org/pg/commitdiff/0ea1f2a3a8dfcbe8062a65a13700fc5ae83482c6

- Move PGAC_LDAP_SAFE to config/programs.m4.  This restores the style
  of keeping configure.in free of AC_DEFUN.  Per gripe from Tom Lane.
  http://git.postgresql.org/pg/commitdiff/e565ff7553e60b3d13dde410ef96f5256c5525eb

- Handle WAIT_IO_COMPLETION return from WaitForMultipleObjectsEx().
  This return code is possible wherever we pass bAlertable = TRUE; it
  arises when Windows caused the current thread to run an "I/O
  completion routine" or an "asynchronous procedure call".  PostgreSQL
  does not provoke either of those Windows facilities, hence this bug
  remaining largely unnoticed, but other local code might do so.  Due
  to a shortage of complaints, no back-patch for now.  Per report from
  Shiv Shivaraju Gowda, this bug can cause PGSemaphoreLock() to PANIC.
  The bug can also cause select() to report timeout expiration too
  early, which might confuse pgstat_init() and CheckRADIUSAuth().
  http://git.postgresql.org/pg/commitdiff/de35a9771004b9d521c9d5882db6be4fba20e80e

Andrew Dunstan pushed:

- Allow empty string object keys in json_object().  This makes the
  behaviour consistent with the json parser, other json-generating
  functions, and the JSON standards.
  http://git.postgresql.org/pg/commitdiff/4ebe3519e1c12fe02f734aa00f824833181840c7

Fujii Masao pushed:

- Fix bug where pg_receivexlog goes into busy loop if -s option is set
  to 0.  The problem is that pg_receivexlog calls select(2) with
  timeout=0 and goes into busy loop when --status-interval option is
  set to 0. This bug was introduced by the commit,
  74cbe966fe2d76de1d607d933c98c144dab58769.  Per report from Sawada
  Masahiko
  http://git.postgresql.org/pg/commitdiff/78493b716802cbe632d36c85f0d7c3bdb708e045

Robert Haas pushed:

- docs: Improve documentation of \pset without arguments.  The syntax
  summary previously failed to clarify that the first argument is also
  optional.  The textual description did mention it, but all the way
  at the bottom.  It fits better with the command overview, so move it
  there, and fix the summary also.  Dilip Kumar, reviewed by Fabien
  Coelho
  http://git.postgresql.org/pg/commitdiff/967a4e7f3107e3c5b732fe4f8e13a1f31a255e46

- Avoid access to already-released lock in LockRefindAndRelease.
  Spotted by Tom Lane.
  http://git.postgresql.org/pg/commitdiff/32d78894c2a92cbb2fe7b9160936fee31672e7d9

- Prevent shm_mq_send from reading uninitialized memory.
  shm_mq_send_bytes didn't invariably initialize *bytes_written before
  returning, which would cause shm_mq_send to read from uninitialized
  memory and add the value it found there to mqh->mqh_partial_bytes.
  This could cause the next attempt to send a message via the queue to
  fail an assertion (if the queue was detached) or copy data from a
  garbage pointer value into the queue (if non-blocking mode was in
  use).
  http://git.postgresql.org/pg/commitdiff/1144ea3421e4bcc24dd7402a1f21ba94638d591b

- Fix checkpointer crash in EXEC_BACKEND builds.  Nothing in the
  checkpointer calls InitXLOGAccess(), so WALInsertLocks never got
  initialized there.  Without EXEC_BACKEND, it works anyway because
  the correct value is inherited from the postmaster, but with
  EXEC_BACKEND we've got a problem.  The problem appears to have been
  introduced by commit 68a2e52bbaf98f136a96b3a0d734ca52ca440a95.  To
  fix, move the relevant initialization steps from InitXLOGAccess() to
  XLOGShmemInit(), making this more parallel to what we do elsewhere.
  Amit Kapila
  http://git.postgresql.org/pg/commitdiff/250c26ba9cf247c2d5b8dbd2435a36d11382c43e

Andres Freund pushed:

- Properly remove ephemeral replication slots after a crash restart.
  Ephemeral slots - slots that shouldn't survive database restarts -
  weren't properly cleaned up after a immediate/crash restart. They
  were ignored in the sense that they weren't restored into memory and
  thus didn't cause unwanted resource retention; but they prevented a
  new slot with the same name from being created.  Now ephemeral slots
  are fully removed during startup.  Backpatch to 9.4 where
  replication slots where added.
  http://git.postgresql.org/pg/commitdiff/93a028f569232fa498279841cb61ad11c2df5c85

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Dilip Kumar sent in another revision of a patch to document correctly
that all arguments to pset are optional, not just the second.

Marko (johto) Tiikkaja sent in a patch to add
plpgsql.extra_warnings='num_into_expressions'

Anastasia Lubennikova sent in another revision of a patch to allow
index-only scans for multicolumn GiST.

Fabien COELHO and Mitsumasa KONDO traded patches to allow pgbench to
use a Gaussian distribution.

Kaigai Kouhei sent in another revision of a patch to enable the custom
plan API.

Pavel Stehule sent in another revision of a patch to enable psql
unicode border line styles.

Viswanatham Kirankumar sent in another revision of a patch to process
pg_hba.conf keywords as case-insensitive.

Fabrízio de Royes Mello sent in two more revisions of a patch to
enable ALTER TABLE ... SET LOGGED.

Kyotaro HORIGUCHI sent in another revision of a patch to enable using
unique indexes for longer pathkeys.

Michael Paquier sent in a patch to add a facility to check
Full-Page-Write consistency at WAL replay.

Thomas Munro sent in four more revisions of a patch to implement SKIP
LOCKED DATA.

Fabrízio de Royes Mello sent in another revision of a patch to fix an
issue where the verbose output of pg_dump did not show schema names.

Furuya Osamu sent in another revision of a patch to add a synchronous
mode to pg_receivexlog.

Kyotaro HORIGUCHI sent in a patch to introduce coarse-grained
parallelism via the postgres_fdw.

Alexey Klyukin sent in a patch to implement subject alternative names
support for SSL connections.

Robert Haas sent in a patch to implement a contrib module that lets
you launch arbitrary command in a background worker, and supporting
infrastructure patches for core.

Guillaume Lelarge sent in a patch to fix the documentation for
unix_socket_directory.

Marko (johto) Tiikkaja sent in a patch to implement EXIT USING
ROLLBACK.

Marko (johto) Tiikkaja sent in a patch to make PL/pgsql throw an error
during compilation (instead of runtime) if the number of parameters
passed to RAISE don't match the number of placeholders in error
message.

Haribabu Kommi sent in another revision of a patch to enable min/max
on inet types.

David Rowley sent in a patch to fix an issue where get_loop_count()
fails to ignore RELOPT_DEADREL rels.

Peter Geoghegan sent in another revision of a patch to add a strxfrm()
optimization for B-Trees.

--

-- 
Sent via pgsql-announce mailing list (pgsql-announce <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-announce

Guillaume Lelarge | 25 Jul 09:25 2014

pgAdmin v.1.20.0 Beta 1 now available

pgAdmin v1.20.0 Beta 1 is now available for testing in source from:

http://www.postgresql.org/ftp/pgadmin3/release/v1.20.0-beta1/

Unfortunately, Windows and Mac OS X distributions aren't yet available. Nevertheless, you can still have it with the PostgreSQL 9.4 beta 2 one-click installer from:

http://www.postgresql.org/download/snapshots/

We're still working on a visual tour. In the meantime, the list of new features is available in the changelog (http://www.pgadmin.org/development/changelog.php).

Please download a copy to test, and report any issues to pgadmin-support(at)postgresql(dot)org to help us prepare for our upcoming 1.20 final release.

Regards.


--

Gmane