David Fetter | 15 Sep 08:26 2014

== PostgreSQL Weekly News - September 14 2014 ==

== PostgreSQL Weekly News - September 14 2014 ==

== PostgreSQL Product News ==

Open PostgreSQL Monitoring (OPM) released.
http://opm.io/

== PostgreSQL Jobs for September ==

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

== PostgreSQL Local ==

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 fifth edition of the Argentinian PostgreSQL Day will be held on
November 28th, 2014 in Santa Fe, Argentina.  The International CfP is
open through September 28th, 2014.
http://www.postgresql.org.ar/pgday2014

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

(Continue reading)

damien clochard | 8 Sep 15:49 2014

Introducing Open PostgreSQL Monitoring (OPM)

# Introducing Open PostgreSQL Monitoring (OPM)

## Oversee and Manage Your PostgreSQL Servers

_Paris, September 8th 2014_

The OPM Development Group (see below) is proud to present the first
public release of Open PostgreSQL Monitoring, a fully open source
monitoring suite for PostgreSQL.

## Get Graphs and Stats from your PostgreSQL instances!

PostgreSQL may be the most advanced database in the world but one of its
biggest handicap is the lack of open source dedicated monitoring tools.
Compared to its competitors, the PostgreSQL community has not been able
to produce tools similar to Oracle Grid Control, MySQL Workbench or SQL
Server Management Studio.

Today we'd like to present the OPM project: a fully open-source suite
designed to provide dynamic graphs, custom stats series, performance
analysis, server health overview and team management...

If you have serveral postgres servers in production, Open PostgreSQL
Monitoring is the perfect to watch the current activity of your
databases, with DBA-centric stats such as: database size, hit ratio,
streaming replication lag, system load, page bloat, longest queries, WAL
files generation, locks, backends status, etc.

## Extensibility is the key

(Continue reading)

David Fetter | 8 Sep 08:57 2014

== PostgreSQL Weekly News - September 07 2014 ==

== PostgreSQL Weekly News - September 07 2014 ==

The fifth edition of the Argentinian PostgreSQL Day will be held on
November 28th, 2014 in Santa Fe, Argentina.  The International CfP is
open through September 28th, 2014.
http://www.postgresql.org.ar/pgday2014

PGDay Campinas 2014 will take place in Campinas on September 10th.
Sign-up is still open.
http://pgdaycampinas.com.br/

== PostgreSQL Product News ==

DSL, a Domain Specification Language compiler designed to allow using
PostgreSQL as an OO data store, released.
https://dsl-platform.com/

pgpool-II 3.3.4, 3.2.9, 3.1.12, and 3.0.16 released.
http://pgpool.net/mediawiki/index.php/Downloads

== PostgreSQL Jobs for September ==

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

== PostgreSQL Local ==

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)

Mariano Reingart | 7 Sep 07:23 2014
Picon

PgDay Argentina 2014: Call for proposals

The fifth edition of the Argentinian PostgreSQL Day will be held on November 28th in Santa Fe, Argentina (South America):

    http://www.postgresql.org.ar/pgday2014

The International Call for Papers is now open.
Each session will last from 30 to 180 minutes, and may be on any topic related to PostgreSQL.
Presentation language can be English, Spanish or Portuguese.
This year we're looking for talks and hands-on tutorials, specially on migrations from propietary databases, success stories, tools, education, training, etc.
The submission deadline is September 28th, 2014.
Selected speakers will be notified on a rolling basis before the deadline or until all slots were full.

Online proposal submission system:
    http://www.postgresql.org.ar/pgday2014/activity/propose

The fundraising campaign for PGDay 2014 has just started.
There are several opportunities for you to join the advertising (including A/V recording, program guide printing and badge, lanyards, folder/bag, or t-shirt sponsorship).
It is also possible to directly sponsor a speaker for the conference, a meeting room or social events.

The organization is being coordinated by the Argentina PostgreSQL Users Group: arpug <at> postgresql.org

For details please contact Martín Marqués, 2014 Event Chair at
    <martin(at)2ndquadrant(dot)com>

Best regards,

Mariano Reingart
PostgreSQL Argentina RC
ar <at> postgresql.org
http://www.postgresql.org.ar/

Tatsuo Ishii | 6 Sep 07:26 2014

pgpool-II 3.3.4, 3.2.9, 3.1.12, and 3.0.16 released

Pgpool Global Development Group is pleased to announce the availability
of pgpool-II 3.3.4, 3.2.9, 3.1.12, and 3.0.16. These are the latest 
stable minor versions of each major versions of pgpool-II.

You can download the source code, installer, RPMs from:
http://pgpool.net/mediawiki/index.php/Downloads

===============================================================================

                        3.3.4 (tokakiboshi) 2014/09/05

* Version 3.3.4

    This is a bugfix release against pgpool-II 3.3.3.

    __________________________________________________________________

* Bug fixes

    - Fix a typo of pgpool.spec (Yugo Nagata)

    - Fix bug that worker child process keeps failing when there's no
      primary backend (Tatsuo Ishii)

      Problem identified and fix contributed by Junegunn Choi.

      See [pgpool-hackers: 471] for more details.

    - Close listen socket when smart shutdown request is made (Tatsuo Ishii)

      When smart shutdown process starts, pgpool children still listen on
      the port and clients can send further connection requests which fail
      in the end. Which is not only waste of time, but also prevents a load
      balancer which sits in front of pgpool from realizing the pgpool is
      going down.

      Problem analyzed and patch provided by Junegunn Choi in [pgpool-hackers
      474], and enhanced to take care not only inet domain socket but UNIX
      domain socket by Tatsuo Ishii.

    - doc: Add cautions that recovery commands are killed by statement_timeout
      of PostgreSQL. (Tatsuo Ishii)

    - test: Fix bug that wait_for_pgpool_startup does not work. (Tatsuo Ishii)

    - test: Fix test driver for watchdog to use wait_for_pgpool_startup correctly
      (Tatsuo Ishii)

    - Fix to ignore a harmless error code when executing ifconfig command
      (Yugo Nagata)

      When executing command such as ifconfig or ping by execv() in a forked
      child proess, wait() can fails with an error code ECHILD, although the
      process exists exactly, if SIGCHLD is set to SIG_IGN in Linux. We should
      ignore this and not treat as failure of the command.

    - test: Add undocumented "-j" option to the script comment. (Tatsuo Ishii)

    - test: Fix unwanted JDBC regression test failure (Tatsuo Ishii)

    - test: Fix to prevent regression test failures on slow machines
      (Tatsuo Ishii)

    - test: Allow to specify PostgreSQL library directory by environment
      variable (Tatsuo Ishii)

    - Adopt PostgreSQL 9.4 having to_regclass (Tatsuo Ishii)

      PostgreSQL 9.4 has built-in function "to_regclass", which has
      equivalent functionality of pgpool_regclass. Now pgpool searches
      to_regclass first then try pgpool_regclass.

    - Fix unportable code related to SO_REUSEPORT (Tatsuo Ishii)

      There are several places using setsockopt(sock, SOL_SOCKET,
      SO_REUSEPORT...). SO_REUSEPORT is not available on all Linux kernels
      and the source code uses ifdef to detect the feature in the compile
      time. Problem is, the binary created with kernel which provides the
      feature cannot run on a kernel which does not provide the feature. Fix
      is, detecting the feature in the run time by checking error code
      returned by setsockopt() and ignore it if the cause of the error is
      lacking the feature.

    - doc: Remove old restriction description which is no longer true
      (Tatsuo Ishii)

    - Fix return type of text_to_lsn() function (Yugo Nagata)

      This caused compile warning.

    - Fix file descriptor leak when daemonize. (Tatsuo Ishii)

      Per Coverity 1111471.

    - Fix memory leak. (Tatsuo Ishii)

      Per Coverity 1111442.

    - Fix pgpool.init's long-standing bug of stop/restart failure
      (Yugo Nagata)

      In previous, pgpool.init uses killproc for stopping pgpool, but there
      are several problems. In the new version, "pgpool -m fast stop" is
      used in stop command.

      Original patch contributed by Ryan DeShone and modified by Yugo Nagata.

      See [pgpool-hackers: 239][pgpool-hackers: 512].

    - Allow to run pgpool_setup and regression test on Ubuntu box
      (Tatsuo Ishii)

    - test: Fix -i option (install directory of pgpool) not working
      (Tatsuo Ishii)

    - Add missing include file sys/wait.h. (Tatsuo Ishii)

      Per bug #104.
      http://www.pgpool.net/mantisbt/view.php?id=104

    - Fix an infinite loop of ping error at new active pgpool when virtual
      IP switching (Yugo Nagata)

      This bug also caused hangs of the old active pgpool, since this waits
      response from the new active pgpool, which is in the infinite loop and
      not able to respond.

      This problem is reported by Qian Peng in [pgpool-hackers: 520].

    - Disbale statement_timeout of PostgreSQL while executing online recovery
      (Tatsuo Ishii)

      Online recovery may take very long time and user may enable statement
      timeout. To prevent online recovery canceled by statement timeout,
      disable statement timeout in the connection used by online recovery.

      See [pgpool-general: 2919] for more details.

    - Fix pool_table_name_to_oid in case new to_regclass used which is
      introduced in PostgreSQL 9.4 (Tatsuo Ishii)

      The relcache func used here should return 0 if target table is not
      found. However to_regclass returns NULL in this case. To fix the
      problem now COALESCE is used.

    - test: Fix regression test 057 hung if run against PostgreSQL 9.4 or
      later (Tatsuo Ishii)

      PostgreSQL 9.4 or later changed libpq behavior: NULL username for
      connection string does not cause an error, which was expected in the
      test.

    - Fix to close pipe when ping command exits with failure (Yugo Nagata)

      This bug causes pipe open error: Too many open files, which
      leads to failure of connecting to trusted servers, and then
      pgpool goes to down status.

    - Fix Resource leaks (Muhammad Usama)

      Coverity issue #1222998 and #1222999.

    - Add a description that pcp_detach_node command disconnects existing
      sessions (Tatsuo Ishii)

    - Fix failover.sh produced by pgpool_setup (Tatsuo Ishii)

      It did not support there's more than 3 nodes case. It always tries to
      promoto node0 or node1.

    - Remove meaningless minus check because of unsigned int variable
      (Tatsuo Ishii)

      Coverity issue #1111419, #1111420, #1111422.

    - replacing strcpy() with much safer and recomended call strlcpy()
      (Muhammad Usama)

      Coverity issue #1111480.

    - Fix pgpool.spec to support openssl (Tatsuo Ishii)

    - Fix pgpool.spec to use 3.3-stable tree head (Tatsuo Ishii)

    - Remove unnecessary call to pool_shmem_exit() which removes semaphore
      when it shouldn't (Tatsuo Ishii)

      exit_handler checks if the process is parent or not. This is
      good. However, even if it is a child process, it calls
      pool_shmem_exit() which removes semaphore and shmem when it should
      not. It should be called only from parent process.

      Per bug #102.
      http://www.pgpool.net/mantisbt/view.php?id=102

    - Fix get_insert_command_table_name() function not to use freed pointer
      (Muhammad Usama)

      Coverity issue #1223007.

    - Fix pool_handle_query_cache() to not free NULL pointer (Tatsuo Ishii)

    - Change connect() timeout longer (10 seconds) for flaky network
      (Tatsuo Ishii)

      Change connect() timeout in connect_inet_domain_socket_by_port() from
      1 second to 10 seconds for flaky network such as AWS. This should help
      reducing frequent failover.

    - Fix reset query stuck problem. (Tatsuo Ishii)

      It is reported that reset query (DISCARD ALL etc.) occasionally does
      not finish and pgpool child remain waiting for reply from backend thus
      client cannot connect to pgpool.

      The cause of problem is not identified yet but if client suddenly
      closes connection to pgpool in the middle of query processing, backend
      may not accept the reset queries because they are not ready for query.

      The fix is, if frontend closes connection in unexpected way, query
      process loop immediately returns with new state:
      POOL_END_WITH_FRONTEND_ERROR and pgpool closes connection to
      PostgreSQL then goes back to new connection request waiting loop.

      Also, pgpool closes connections to backend when client_idle_limit is
      set and the idle limit.

      Per bug #107.
      http://www.pgpool.net/mantisbt/view.php?id=107

    - Fix other dozens of coverity issues (Muhammad Usama)

===============================================================================

                        3.2.9 (namameboshi) 2014/09/05

* Version 3.2.9

    This is a bugfix release against pgpool-II 3.2.8.

    __________________________________________________________________

* Bug fixes

    - Fix a typo of pgpool.spec (Yugo Nagata)

    - Fix bug that worker child process keeps failing when there's no
      primary backend (Tatsuo Ishii)

      Problem identified and fix contributed by Junegunn Choi.

      See [pgpool-hackers: 471] for more details.

    - Close listen socket when smart shutdown request is made (Tatsuo Ishii)

      When smart shutdown process starts, pgpool children still listen on
      the port and clients can send further connection requests which fail
      in the end. Which is not only waste of time, but also prevents a load
      balancer which sits in front of pgpool from realizing the pgpool is
      going down.

      Problem analyzed and patch provided by Junegunn Choi in [pgpool-hackers
      474], and enhanced to take care not only inet domain socket but UNIX
      domain socket by Tatsuo Ishii.

    - doc: Add cautions that recovery commands are killed by statement_timeout
      of PostgreSQL. (Tatsuo Ishii)

    - doc: Remove old restriction description which is no longer true
      (Tatsuo Ishii)

    - Fix return type of text_to_lsn() function (Yugo Nagata)

      This caused compile warning.

    - Fix file descriptor leak when daemonize. (Tatsuo Ishii)

      Per Coverity 1111471.

    - Fix memory leak. (Tatsuo Ishii)

      Per Coverity 1111442.

    - Fix pgpool.init's long-standing bug of stop/restart failure
      (Yugo Nagata)

      In previous, pgpool.init uses killproc for stopping pgpool, but there
      are several problems. In the new version, "pgpool -m fast stop" is
      used in stop command.

      Original patch contributed by Ryan DeShone and modified by Yugo Nagata.

      See [pgpool-hackers: 239][pgpool-hackers: 512].

    - Add missing include file sys/wait.h. (Tatsuo Ishii)

      Per bug #104.
      http://www.pgpool.net/mantisbt/view.php?id=104

    - Disbale statement_timeout of PostgreSQL while executing online recovery
      (Tatsuo Ishii)

      Online recovery may take very long time and user may enable statement
      timeout. To prevent online recovery canceled by statement timeout,
      disable statement timeout in the connection used by online recovery.

      See [pgpool-general: 2919] for more details.

    - Remove unnecessary call to pool_shmem_exit() which removes semaphore
      when it shouldn't (Tatsuo Ishii)

      exit_handler checks if the process is parent or not. This is
      good. However, even if it is a child process, it calls
      pool_shmem_exit() which removes semaphore and shmem when it should
      not. It should be called only from parent process.

      Per bug #102.
      http://www.pgpool.net/mantisbt/view.php?id=102

===============================================================================

                        3.1.12 (hatsuiboshi) 2014/09/05

* Version 3.1.12

    This is a bugfix release against pgpool-II 3.1.11.

    __________________________________________________________________

* Bug fixes

    - Fix a typo of pgpool.spec (Yugo Nagata)

    - Fix bug that worker child process keeps failing when there's no
      primary backend (Tatsuo Ishii)

      Problem identified and fix contributed by Junegunn Choi.

      See [pgpool-hackers: 471] for more details.

    - Close listen socket when smart shutdown request is made (Tatsuo Ishii)

      When smart shutdown process starts, pgpool children still listen on
      the port and clients can send further connection requests which fail
      in the end. Which is not only waste of time, but also prevents a load
      balancer which sits in front of pgpool from realizing the pgpool is
      going down.

      Problem analyzed and patch provided by Junegunn Choi in [pgpool-hackers
      474], and enhanced to take care not only inet domain socket but UNIX
      domain socket by Tatsuo Ishii.

    - doc: Add cautions that recovery commands are killed by statement_timeout
      of PostgreSQL. (Tatsuo Ishii)

    - doc: Remove old restriction description which is no longer true
      (Tatsuo Ishii)

    - Fix return type of text_to_lsn() function (Yugo Nagata)

      This caused compile warning.

    - Fix file descriptor leak when daemonize. (Tatsuo Ishii)

      Per Coverity 1111471.

    - Fix memory leak. (Tatsuo Ishii)

      Per Coverity 1111442.

    - Fix pgpool.init's long-standing bug of stop/restart failure
      (Yugo Nagata)

      In previous, pgpool.init uses killproc for stopping pgpool, but there
      are several problems. In the new version, "pgpool -m fast stop" is
      used in stop command.

      Original patch contributed by Ryan DeShone and modified by Yugo Nagata.

      See [pgpool-hackers: 239][pgpool-hackers: 512].

    - Disbale statement_timeout of PostgreSQL while executing online recovery
      (Tatsuo Ishii)

      Online recovery may take very long time and user may enable statement
      timeout. To prevent online recovery canceled by statement timeout,
      disable statement timeout in the connection used by online recovery.

      See [pgpool-general: 2919] for more details.

    - Remove unnecessary call to pool_shmem_exit() which removes semaphore
      when it shouldn't (Tatsuo Ishii)

      exit_handler checks if the process is parent or not. This is
      good. However, even if it is a child process, it calls
      pool_shmem_exit() which removes semaphore and shmem when it should
      not. It should be called only from parent process.

      Per bug #102.
      http://www.pgpool.net/mantisbt/view.php?id=102

===============================================================================

                        3.0.16 (umiyameboshi) 2014/09/05

* Version 3.0.16

    This is a bugfix release against pgpool-II 3.0.15.

    __________________________________________________________________

* Bug fixes

    - Fix a typo of pgpool.spec (Yugo Nagata)

    - Fix bug that worker child process keeps failing when there's no
      primary backend (Tatsuo Ishii)

      Problem identified and fix contributed by Junegunn Choi.

      See [pgpool-hackers: 471] for more details.

    - Close listen socket when smart shutdown request is made (Tatsuo Ishii)

      When smart shutdown process starts, pgpool children still listen on
      the port and clients can send further connection requests which fail
      in the end. Which is not only waste of time, but also prevents a load
      balancer which sits in front of pgpool from realizing the pgpool is
      going down.

      Problem analyzed and patch provided by Junegunn Choi in [pgpool-hackers
      474], and enhanced to take care not only inet domain socket but UNIX
      domain socket by Tatsuo Ishii.

    - doc: Add cautions that recovery commands are killed by statement_timeout
      of PostgreSQL. (Tatsuo Ishii)

    - doc: Remove old restriction description which is no longer true
      (Tatsuo Ishii)

    - Fix return type of text_to_lsn() function (Yugo Nagata)

      This caused compile warning.

    - Fix file descriptor leak when daemonize. (Tatsuo Ishii)

      Per Coverity 1111471.

    - Fix memory leak. (Tatsuo Ishii)

      Per Coverity 1111442.

    - Fix pgpool.init's long-standing bug of stop/restart failure
      (Yugo Nagata)

      In previous, pgpool.init uses killproc for stopping pgpool, but there
      are several problems. In the new version, "pgpool -m fast stop" is
      used in stop command.

      Original patch contributed by Ryan DeShone and modified by Yugo Nagata.

      See [pgpool-hackers: 239][pgpool-hackers: 512].

    - Disbale statement_timeout of PostgreSQL while executing online recovery
      (Tatsuo Ishii)

      Online recovery may take very long time and user may enable statement
      timeout. To prevent online recovery canceled by statement timeout,
      disable statement timeout in the connection used by online recovery.

      See [pgpool-general: 2919] for more details.

    - Remove unnecessary call to pool_shmem_exit() which removes semaphore
      when it shouldn't (Tatsuo Ishii)

      exit_handler checks if the process is parent or not. This is
      good. However, even if it is a child process, it calls
      pool_shmem_exit() which removes semaphore and shmem when it should
      not. It should be called only from parent process.

      Per bug #102.
      http://www.pgpool.net/mantisbt/view.php?id=102

===============================================================================

--

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

Rikard Pavelic | 4 Sep 13:05 2014
Picon

DSL Platform goes live

We are proud to announce our Domain Specification Language compiler out of beta with numerous BSD licensed
libraries and more transparent DB migrations.

DSL is a starting point which is used to describe the model, based on Domain-Driven Design and with building
blocks such as aggregate root, entity, value object, snowflake, olap cube, etc...

This allows you to use Postgres in a more object-oriented way, while avoiding pain points of dependency
invalidation and complex migrations which are encountered when using Postgres as an ORDBMS.

Online DSL compiler is free to use tool, which will use Invasive software composition to glue various
libraries together based on provided DSL model. SQL migrations are created by diff analysis of
previous and current DSL model.

Links of interest:
 * Revenj (.NET backend): https://github.com/ngs-doo/revenj
   - contains advanced Postgres LINQ driver
 * PHP DSL admin: https://github.com/ngs-doo/dsl-admin-php
   - Administrative web interface for data based on the DSL model
 * Visual Studio plugin: http://visualstudiogallery.msdn.microsoft.com/5b8a140c-5c84-40fc-a551-b255ba7676f4
   - syntax highlighter and DSL compiler UI tool
 * Command line client: https://github.com/ngs-doo/dsl-compiler-client
   - console tool for interaction with the compiler
 * Various HTTP clients (PHP, Java, Scala): https://github.com/ngs-doo

and various others, such as: Eclipse plugin, Scala server, ...

If you have any questions, I will be happy to answer them.

Regards,
Rikard

-- 
Rikard Pavelic
https://dsl-platform.com/

--

-- 
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 | 1 Sep 08:16 2014

== PostgreSQL Weekly News - August 31 2014 ==

== PostgreSQL Weekly News - August 31 2014 ==

== PostgreSQL Product News ==

psycopg2 2.5.4, a Python connector for PostgreSQL, released.
http://initd.org/psycopg/articles/2014/08/30/psycopg-254-released/

== 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:

- Don't track DEALLOCATE in pg_stat_statements.  We also don't track
  PREPARE, nor do we track planning time in general, so let's ignore
  DEALLOCATE as well for consistency.  Backpatch to 9.4, but not
  further than that. Although it seems unlikely that anyone is relying
  on the current behavior, this is a behavioral change.  Fabien Coelho
  http://git.postgresql.org/pg/commitdiff/3cd934f635699b7c8b0027be69fddfc36be6f9b8

- Show schema names in pg_dump verbose output.  Fabrízio de Royes
  Mello, reviewed by Michael Paquier
  http://git.postgresql.org/pg/commitdiff/2bde29739d1e28f58e901b7e53057b8ddc0ec286

- Implement IF NOT EXISTS for CREATE SEQUENCE.  Fabrízio de Royes
  Mello
  http://git.postgresql.org/pg/commitdiff/0076f264b6f24854219d49b159602e2042c38ee7

- Add regression tests for SELECT FOR UPDATE/SHARE NOWAIT.  Thomas
  Munro
  http://git.postgresql.org/pg/commitdiff/9ee16b49f0aac819bd4823d9b94485ef608b34e8

- Fix bug in compressed GIN data leaf page splitting code.  The list
  of posting lists it's dealing with can contain placeholders for
  deleted posting lists. The placeholders are kept around so that they
  can be WAL-logged, but we must be careful to not try to access them.
  This fixes bug #11280, reported by Mårten Svantesson. Backpatch to
  9.4, where the compressed data leaf page code was added.
  http://git.postgresql.org/pg/commitdiff/88231ec5784a00ce406553276be8a5a443dd3ba0

Andres Freund pushed:

- Fix typos in some error messages thrown by extension scripts when
  fed to psql.  Some of the many error messages introduced in 458857cc
  missed 'FROM unpackaged'. Also e016b724 and 45ffeb7e forgot to quote
  extension version numbers.  Backpatch to 9.1, just like 458857cc
  which introduced the messages.  Do so because the error messages
  thrown when the wrong command is copy & pasted aren't easy to
  understand.
  http://git.postgresql.org/pg/commitdiff/d153b801611f6fdc58c7941e85dddb0cb25ca4ef

- Specify the port in dblink and postgres_fdw tests.  That allows to
  run those tests against a postmaster listening on a nonstandard port
  without requiring to export PGPORT in postmaster's environment.
  This still doesn't support connecting to a nondefault host without
  configuring it in postmaster's environment. That's harder and less
  frequently used though. So this is a useful step.
  http://git.postgresql.org/pg/commitdiff/57ca1d4f0175f60e9cfb0f997c864173d9c72607

- Don't hardcode contrib_regression dbname in postgres_fdw and dblink
  tests.  That allows parallel installcheck to succeed inside
  contrib/. The output is not particularly pretty unless make's -O
  option to synchronize the output is used.  There's other tests,
  outside contrib, that use a hardcoded, non-unique, database name.
  Those prohibit paralell installcheck to be used across more
  directories; but that's something for a separate patch.
  http://git.postgresql.org/pg/commitdiff/ddc2504dbcf2af97b58a91b071768c17774d58d1

- Mark IsBinaryUpgrade as PGDLLIMPORT to fix windows builds after
  a7ae1dc.  Author: David Rowley
  http://git.postgresql.org/pg/commitdiff/5569d75d6a82f0d11d26404fceb848ae59869126

- Allow escaping of option values for options passed at connection
  start.  This is useful to allow to set GUCs to values that include
  spaces; something that wasn't previously possible. The primary case
  motivating this is the desire to set default_transaction_isolation
  to 'repeatable read' on a per connection basis, but other usecases
  like seach_path do also exist.  This introduces a slight backward
  incompatibility: Previously a \ in an option value would have been
  passed on literally, now it'll be taken as an escape.  The relevant
  mailing list discussion starts with
  20140204125823.GJ12016 <at> awork2.anarazel.de.
  http://git.postgresql.org/pg/commitdiff/11a020eb6e4023a1570a2788ba22dd6aafbd02dc

- Make backend local tracking of buffer pins memory efficient.  Since
  the dawn of time (aka Postgres95) multiple pins of the same buffer
  by one backend have been optimized not to modify the shared refcount
  more than once. This optimization has always used a NBuffer sized
  array in each backend keeping track of a backend's pins.  That array
  (PrivateRefCount) was one of the biggest per-backend memory
  allocations, depending on the shared_buffers setting. Besides the
  waste of memory it also has proven to be a performance bottleneck
  when assertions are enabled as we make sure that there's no
  remaining pins left at the end of transactions. Also, on servers
  with lots of memory and a correspondingly high shared_buffers
  setting the amount of random memory accesses can also lead to poor
  cpu cache efficiency.  Because of these reasons a backend's buffers
  pins are now kept track of in a small statically sized array that
  overflows into a hash table when necessary. Benchmarks have shown
  neutral to positive performance results with considerably lower
  memory usage.  Patch by me, review by Robert Haas.  Discussion:
  20140321182231.GA17111 <at> alap3.anarazel.de
  http://git.postgresql.org/pg/commitdiff/4b4b680c3d6d8485155d4d4bf0a92d3a874b7a65

- Declare two variables in snapbuild.c as static.  Neither is accessed
  externally, I just seem to have missed the static when writing the
  code.
  http://git.postgresql.org/pg/commitdiff/8fff977e29cda7c1641c43f9b293134adc77b65a

- Protect definition of SpinlockSemaArray, just like its declaration.
  Found via clang's -Wmissing-variable-declarations.
  http://git.postgresql.org/pg/commitdiff/5c1faa7ba729c780b0ac598dbc23dbb1d6e1b872

- Declare lwlock.c's LWLockAcquireCommon() as a static inline.
  68a2e52bbaf98f136 has introduced LWLockAcquireCommon() containing
  the previous contents of LWLockAcquire() plus added functionality.
  The latter then calls it, just like LWLockAcquireWithVar(). Because
  the majority of callers don't need the added functionality, declare
  the common code as inline. The compiler then can optimize away the
  unused code. Doing so is also useful when looking at profiles, to
  differentiate the users.  Backpatch to 9.4, the first branch to
  contain LWLockAcquireCommon().
  http://git.postgresql.org/pg/commitdiff/9c4b55db1dc901dc184b1b3ab9cca3f2089ec311

Alvaro Herrera pushed:

- Editorial review of SET UNLOGGED.  Add a succint comment explaining
  why it's correct to change the persistence in this way.  Also
  s/loggedness/persistence/ because native speakers didn't like the
  latter term.  Fabrízio and Álvaro
  http://git.postgresql.org/pg/commitdiff/7636c0c821f669e134a0f2fd1c6225bb3ec820d4

- Revert XactLockTableWait context setup in conditional multixact
  wait.  There's no point in setting up a context error callback when
  doing conditional lock acquisition, because we never actually wait
  and so the user wouldn't be able to see the context message
  anywhere.  In fact, this is more in line with what
  ConditionalXactLockTableWait is doing.  Backpatch to 9.4, where this
  was added.
  http://git.postgresql.org/pg/commitdiff/3adba736620c85112e0f9f6d043d3574e1c5830f

- More psprintf goodness
  http://git.postgresql.org/pg/commitdiff/d6d6020f1cf33a63bbae59d370b75fa5e98017f0

- Oops, forgot to "git add" one last change
  http://git.postgresql.org/pg/commitdiff/ac41769fd9dca9f4a6ee5fa859a56c08e8bb95fe

- Have CREATE TABLE AS and REFRESH return an OID Other DDL commands
  are already returning the OID, which is required for future
  additional event trigger work.  This is merely making these commands
  in line with the rest of utility command support.
  http://git.postgresql.org/pg/commitdiff/301fcf33eb7fcbcf1da113dabeed90b8eaf656eb

- Use newly added InvalidCommandId instead of 0.  The symbol was added
  by 71901ab6d; the original code was introduced by 6868ed749.
  Development of both overlapped which is why we apparently failed to
  notice.  This is a (very slight) behavior change, so I'm not
  backpatching this to 9.4 for now, even though the symbol does exist
  there.
  http://git.postgresql.org/pg/commitdiff/6f822952eea112d3e19a0ddaad32e99d1943f29d

- DefineType: return base type OID, not its array.  Event triggers
  want to know the OID of the interesting object created, which is the
  main type.  The array created as part of the operation is just a
  subsidiary object which is not of much interest.
  http://git.postgresql.org/pg/commitdiff/832a12f65e91d4295be73e26079aa8508de0cf32

- Fix FOR UPDATE NOWAIT on updated tuple chains.  If SELECT FOR UPDATE
  NOWAIT tries to lock a tuple that is concurrently being updated, it
  might fail to honor its NOWAIT specification and block instead of
  raising an error.  Fix by adding a no-wait flag to EvalPlanQualFetch
  which it can pass down to heap_lock_tuple; also use it in
  EvalPlanQualFetch itself to avoid blocking while waiting for a
  concurrent transaction.  Authors: Craig Ringer and Thomas Munro,
  tweaked by Alvaro Herrera 
  http://www.postgresql.org/message-id/51FB6703.9090801 <at> 2ndquadrant.com
  Per Thomas Munro in the course of his SKIP LOCKED feature
  submission, who also provided one of the isolation test specs.
  Backpatch to 9.4, because that's as far back as it applies without
  conflicts (although the bug goes all the way back).  To that branch
  also backpatch Thomas Munro's new NOWAIT test cases, committed in
  master by Heikki as commit 9ee16b49f0aac819bd4823d9b94485ef608b34e8
  .
  http://git.postgresql.org/pg/commitdiff/1c9701cfe58267cf5d79543a42ee4f0967cc73ab

Bruce Momjian pushed:

- upgrade docs:  highlight pg_upgrade, warn about globals
  preservation.  Also, remove OID preservation mention, mention
  non-text dump formats Backpatch through 9.4
  http://git.postgresql.org/pg/commitdiff/bf1c866597a0e59a30b13a66f3ae505655b61853

- pg_ctl, pg_upgrade:  allow multiple -o/-O options, append them.
  Report by Pavel Raiskup
  http://git.postgresql.org/pg/commitdiff/ebe30ad59bb2d127f576be07e036a473999c4b80

- pg_upgrade:  add SET log_min_error_statement = warning.  Add to
  commit 73d78e11a0f7183c80b93eefbbb6026fe9664015
  http://git.postgresql.org/pg/commitdiff/b0488e5c4fbfdce8acc989bdc17d9f0ec09ac281

- pg_upgrade:  remove support for 8.3 old clusters.  This trims down
  the code, and is in preparation for hardening pg_upgrade against
  auto-oid assignment.
  http://git.postgresql.org/pg/commitdiff/2209b3923a7afe0b6033ecfea972219df252ca8e

- revert "Throw error for ALTER TABLE RESET of an invalid option".
  Reverts commits 73d78e11a0f7183c80b93eefbbb6026fe9664015 and
  b0488e5c4fbfdce8acc989bdc17d9f0ec09ac281.  Also reverts pg_upgrade
  changes.
  http://git.postgresql.org/pg/commitdiff/6cb74a67e26523eb2408f441bfc589c80f76c465

- Throw error for ALTER TABLE RESET of an invalid option.  Also adjust
  pg_upgrade to not use this method for optional TOAST table creation.
  Patch by Fabrízio de Royes Mello
  http://git.postgresql.org/pg/commitdiff/73d78e11a0f7183c80b93eefbbb6026fe9664015

- pg_upgrade docs:  update docs for 8.3 support removal
  http://git.postgresql.org/pg/commitdiff/e8c81b1b8e51475dd5a787660e6754c4bafbff47

- pg_upgrade:  use CTE query rather than temp table.  Now that 8.3 is
  not supported, we can use a CTE and not temp tables.  This allows
  for auto-oid assignment protection in a future patch.
  http://git.postgresql.org/pg/commitdiff/5d16332e96977d8166ea631891f6e2cf3ff11f45

- rename macro isTempOrToastNamespace to isTempOrTempToastNamespace.
  Done for clarity
  http://git.postgresql.org/pg/commitdiff/73fe87503f23144a27f0bdecc55587deb5aa425f

- pg_upgrade:  prevent automatic oid assignment.  Prevent automatic
  oid assignment when in binary upgrade mode.  Also throw an error
  when contrib/pg_upgrade_support functions are called when not in
  binary upgrade mode.  This prevent automatically-assigned oids from
  conflicting with later pre-assigned oids coming from the old
  cluster.  It also makes sure oids are preserved in call important
  cases.
  http://git.postgresql.org/pg/commitdiff/a7ae1dcf4939cf643c5abe8dd673e4b87a6efd42

- pg_is_xlog_replay_paused():  remove super-user-only restriction.
  Also update docs to mention which function are super-user-only.
  Report by sys-milan <at> statpro.com Backpatch through 9.4
  http://git.postgresql.org/pg/commitdiff/01363beae52700c7425cb2d2452177133dad3e93

- Update C comment for pg_attribute.attislocal.  Indicates if column
  has ever been local/non-inherited
  http://git.postgresql.org/pg/commitdiff/c6eaa880eea67a711b30903a9ee2e996bccb775e

- Again update C comments for pg_attribute.attislocal
  http://git.postgresql.org/pg/commitdiff/d5d7d07765443175a49441bad7a799dedc072511

Kevin Grittner pushed:

- Fix superuser concurrent refresh of matview owned by another.  Use
  SECURITY_LOCAL_USERID_CHANGE while building temporary tables; only
  escalate to SECURITY_RESTRICTED_OPERATION while potentially running
  user-supplied code.  The more secure mode was preventing temp table
  creation.  Add regression tests to cover this problem.  This fixes
  Bug #11208 reported by Bruno Emanuel de Andrade Silva.  Backpatch to
  9.4, where the bug was introduced.
  http://git.postgresql.org/pg/commitdiff/a9d0f1cff3fb10151be05be61d24ac9b680c170c

- doc: Various typo/grammar fixes.  Errors detected using Topy
  (https://github.com/intgr/topy), all changes verified by hand and
  some manual tweaks added.  Marti Raudsepp Individual changes
  backpatched, where applicable, as far as 9.0.
  http://git.postgresql.org/pg/commitdiff/05258761bf12a64befc9caec1947b254cdeb74c5

Robert Haas pushed:

- Fix typo in b34e37bfefbed1bf9396dde18f308d8b96fd176c.  Spotted by
  Peter Geoghegan.
  http://git.postgresql.org/pg/commitdiff/9522ec3e707a93d25a99e477af76d7b186fe20de

Peter Eisentraut pushed:

- Fix whitespace
  http://git.postgresql.org/pg/commitdiff/2d759341d97eb863477d6170a84c24ade570f567

- doc: Document valid checkpoint_timeout range.  Author: Fabien COELHO
  <coelho <at> cri.ensmp.fr>
  http://git.postgresql.org/pg/commitdiff/8e484bc4abccc03d49af25d32a5ffaecd3c6cf2d

- Assorted message improvements
  http://git.postgresql.org/pg/commitdiff/65c9dc231a261691c76550f61f5b22f954dfcfd5

- doc: Revert ALTER TABLESPACE summary line.  It was changed when
  ALTER TABLESPACE / MOVE was added but then not updated when that was
  moved back out.
  http://git.postgresql.org/pg/commitdiff/14b7c8f2d062d50f2ad5d306c5cc26b7ec5cf11e

Stephen Frost pushed:

- Fix Var handling for security barrier views.  In some cases, not all
  Vars were being correctly marked as having been modified for
  updatable security barrier views, which resulted in invalid plans
  (eg: when security barrier views were created over top of
  inheiritance structures).  In passing, be sure to update both
  varattno and varonattno, as _equalVar won't consider the Vars
  identical otherwise.  This isn't known to cause any issues with
  updatable security barrier views, but was noticed as missing while
  working on RLS and makes sense to get fixed.  Back-patch to 9.4
  where updatable security barrier views were introduced.
  http://git.postgresql.org/pg/commitdiff/e414ba93add966dfe03e22994764e718ed89ee98

Fujii Masao pushed:

- Add header comments to receivelog.h and streamutil.h.  This commit
  also adds the include guards to those header files.  Michael Paquier
  http://git.postgresql.org/pg/commitdiff/9a2d94892f6a793d52ebabb8283b98a6e3ede3d6

- Revert "Allow units to be specified in relation option setting
  value." This reverts commit
  e23014f3d40f7d2c23bc97207fd28efbe5ba102b.  As the side effect of the
  reverted commit, when the unit is specified, the reloption was
  stored in the catalog with the unit.  This broke pg_dump
  (specifically, it prevented pg_dump from outputting restorable
  backup regarding the reloption) and turned the buildfarm red. Revert
  the commit until the fixed version is ready.
  http://git.postgresql.org/pg/commitdiff/9df492664a74a948c87232f523eea637920a516b

- Allow units to be specified in relation option setting value.  This
  introduces an infrastructure which allows us to specify the units
  like ms (milliseconds) in integer relation option, like GUC
  parameter.  Currently only autovacuum_vacuum_cost_delay reloption
  can accept the units.  Reviewed by Michael Paquier
  http://git.postgresql.org/pg/commitdiff/e23014f3d40f7d2c23bc97207fd28efbe5ba102b

Jeff Davis pushed:

- Allow multibyte characters as escape in SIMILAR TO and SUBSTRING.
  Previously, only a single-byte character was allowed as an escape.
  This patch allows it to be a multi-byte character, though it still
  must be a single character.  Reviewed by Heikki Linnakangas and Tom
  Lane.
  http://git.postgresql.org/pg/commitdiff/8167a3883a3c49f2f77785f8e5f638920c9f14ef

Tom Lane pushed:

- Fix citext upgrade script for disallowance of oidvector element
  assignment.  In commit 45e02e3232ac7cc5ffe36f7986159b5e0b1f6fdc, we
  intentionally disallowed updates on individual elements of oidvector
  columns.  While that still seems like a sane idea in the abstract,
  we (I) forgot that citext's "upgrade from unpackaged" script did in
  fact perform exactly such updates, in order to fix the problem that
  citext indexes should have a collation but would not in databases
  dumped or upgraded from pre-9.1 installations.  Even if we wanted to
  add casts to allow such updates, there's no practical way to do so
  in the back branches, so the only real alternative is to make
  citext's kluge even klugier.  In this patch, I cast the oidvector to
  text, fix its contents with regexp_replace, and cast back to
  oidvector.  (Ugh!) Since the aforementioned commit went into all
  active branches, we have to fix this in all branches that contain
  the now-broken update script.  Per report from Eric Malm.
  http://git.postgresql.org/pg/commitdiff/7f7eec89b66947e4098773cf286653b9c4f01c88

- Add min and max aggregates for inet/cidr data types.  Haribabu
  Kommi, reviewed by Muhammad Asif Naeem
  http://git.postgresql.org/pg/commitdiff/6c40f8316ed38a92049784b3e3d3b514ed379b5a

Noah Misch pushed:

- Always use our getaddrinfo.c on Windows.  Commit
  a16bac36eca8158cbf78987e95376f610095f792 let "configure" detect the
  system getaddrinfo() when building under 64-bit MinGW-w64.  However,
  src/include/port/win32/sys/socket.h assumes all native Windows
  configurations use our replacement.  This change placates buildfarm
  member jacana until we establish a plan for getaddrinfo() on
  Windows.
  http://git.postgresql.org/pg/commitdiff/ec544a65c9090bc9da11ea384d1369fd552ca8b0

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

SAWADA Masahiko sent in a WIP patch to add "-C (--concurrently)"
option for reindexdb command for concurrently reindexing.

Andrew (RhodiumToad) Gierth sent in three more revisions of a patch to
add GROUPING SETS and make necessary associated changes to the contrib
code.

Andres Freund sent in a patch to add .NOTPARALLEL to contrib/Makefile.

Fujii Masao sent in another revision of a patch to specify the unit
in storage parameters.

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

Petr (PJMODOS) Jelinek and Tom Lane traded patches to add built-in
binning functions.

Michael Paquier sent in another revision of a patch to ensure that
pg_dump shows the schema name.

Alvaro Herrera sent in another revision of a patch to replicate DROP
commands across servers.

Michael Paquier sent in another revision of a patch to implement
REINDEX CONCURRENTLY.

Michael Paquier sent in two more revisions of a patch to add a missing
comment block at the top of streamutil.h and receivelog.h.

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

Tom Lane and Arthur Silva traded patches to fix a situation where
JSONB's structure plays poorly with TOAST compression.

Fujii Masao sent in two more revisions of a patch to add a GUC for
logging replication commands.

Andres Freund sent in two more revisions of a patch to make backend
local tracking of buffer pins memory efficient.

Alvaro Herrera sent in a patch to introduce a "delay equivalent" to
sort out some oddness in autovacuum cost calculations.

Kevin Grittner sent in two more revisions of a patch to implement
delta relations, among other places, in AFTER triggers.

Fabien COELHO sent in six more revisions of a patch to implement a
pgbench throttling latency limit.

Andres Freund and SAWADA Masahiko traded patches to add line number as
an optional prompt in psql.

Joachim Wieland sent in another revision of a patch to refactor
pg_dump to remove global variables.

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

Emre Hasegeli sent in three more revisions of a patch to add
selectivity estimation for inet operators.

Michael Paquier sent in a patch to simplify calls of pg_class_aclcheck
when multiple modes are used.

Fujii Masao and Amit Kapila traded patches to allow auditing logout.

Pavel Stehule and Andres Freund traded patches to give access to
help_variables and usage from psql via psql command.

Peter Geoghegan sent in a patch to extend the INSERT statement, adding
a new ON CONFLICT {UPDATE | IGNORE} clause.

Julien Rouhaud sent in another revision of a patch to track the number
of files ready to be archived in pg_stat_archiver.

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

Heikki Linnakangas and Andres Freund traded patches to make the
bgwriter do a better job of controlling latency.

Michael Paquier sent in another revision of a patch to enable support
for N synchronous standby servers, N>1.

Etsuro Fujita sent in another revision of a patch to implement INHERIT
support for foreign tables.

Amit Kapila sent in another revision of a patch to permit scaling
shared buffer eviction.

Kyotaro HORIGUCHI sent in another revision of a patch to fix some
brokein code around socket emulation on win32.

Alvaro Herrera sent in another revision of a patch to create a better
REINDEX syntax.

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

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

Fujii Masao sent in a patch to fix an infelicity in psql's \watch vs.
\timing.

Craig Ringer sent in a patch to allow distdir to be overridden on the
"make" command line.

Ali Akbar sent in a patch to fix xpath() to return namespace
definitions.

Amit Kapila sent in another revision of a patch to implement ALTER
SYSTEM RESET.

Michael Paquier sent in two more revisions of a patch to fix a
misleading error message in logical decoding for binary plugins.

Adam Brightwell sent in another revision of a patch to provide the
capability to create multiple named row level security policies for a
table on a per command basis and assign them to be applied to specific
roles/users.

Ali Akbar sent in another revision of a patch to accept empty values
as xml "content" values.

Peter Eisentraut sent in another revision of a patch to improve the
speed of "make check-world".

--

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

Daniele Varrazzo | 30 Aug 21:01 2014
Picon

Psycopg 2.5.4 released

Psycopg 2.5.4 has been released. You can get it from:

http://initd.org/psycopg/tarballs/PSYCOPG-2-5/psycopg2-2.5.4.tar.gz

Signature: http://initd.org/psycopg/tarballs/PSYCOPG-2-5/psycopg2-2.5.4.tar.gz.asc

This version supports the new jsonb PostgreSQL type out-of-the-box.
And of course there are a few bug fixed:

- Fixed segfault if COPY statements are passed to 'execute()' instead
  of using the proper methods (ticket #219).
- Force conversion of pool arguments to integer to avoid potentially
  unbounded pools (ticket #220).
- Cursors WITH HOLD don't begin a new transaction upon
  move/fetch/close (ticket #228).
- Cursors WITH HOLD can be used in autocommit (ticket #229).
- 'callproc()' doesn't silently ignore an argument without a length.
- Fixed memory leak with large objects (ticket #256).
- The internal '_psycopg.so' module can be imported stand-alone
  (to allow modules juggling such as the one described in ticket #201).

Have a good weekend!

----

Psycopg is the most popular PostgreSQL adapter for the Python
programming language. At its core it fully implements the Python DB
API 2.0 specifications. Several extensions allow access to many of the
features offered by PostgreSQL.

--

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

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
serve basis. See the training section on the website for details.

We look forward to seeing you in Madrid!

--

-- 
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 | 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/

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 mention of non-int64 support in CREATE SEQUENCE
  documentation.  The old text explained what happened if we didn't
  have working int64 arithmetic.  Since that case has been explicitly
  rejected by configure since 8.4.3, documenting it in the 9.x
  branches can only produce confusion.
  http://git.postgresql.org/pg/commitdiff/2b475c5946bc8a9beaff3f57b45cc440a78561a1

- Fix core dump in jsonb #> operator, and add regression test cases.
  jsonb's #> operator segfaulted (dereferencing a null pointer) if the
  RHS was a zero-length array, as reported in bug #11207 from Justin
  Van Winkle.  json's #> operator returns NULL in such cases, so for
  the moment let's make jsonb act likewise.  Also add a bunch of
  regression test queries memorializing the -> and #> operators'
  behavior for this and other corner cases.  There is a good argument
  for changing some of these behaviors, as they are not very
  consistent with each other, and throwing an error isn't necessarily
  a desirable behavior for operators that are likely to be used in
  indexes.  However, everybody can agree that a core dump is the Wrong
  Thing, and we need test cases even if we decide to change their
  expected output later.
  http://git.postgresql.org/pg/commitdiff/9bac66020db75871463bafdb394568bf946e8991

- More regression test cases for json/jsonb extraction operators.
  Cover some cases I omitted before, such as null and empty-string
  elements in the path array.  This exposes another inconsistency:
  json_extract_path complains about empty path elements but
  jsonb_extract_path does not.
  http://git.postgresql.org/pg/commitdiff/fa069822f5a02bbbe46bada0b6e420a89c5f7484

- Fix corner-case behaviors in JSON/JSONB field extraction operators.
  Cause the path extraction operators to return their lefthand input,
  not NULL, if the path array has no elements.  This seems more
  consistent since the case ought to correspond to applying the simple
  extraction operator (->) zero times.  Cause other corner cases in
  field/element/path extraction to return NULL rather than failing.
  This behavior is arguably more useful than throwing an error, since
  it allows an expression index using these operators to be built even
  when not all values in the column are suitable for the extraction
  being indexed.  Moreover, we already had multiple inconsistencies
  between the path extraction operators and the simple extraction
  operators, as well as inconsistencies between the JSON and JSONB
  code paths.  Adopt a uniform rule of returning NULL rather than
  throwing an error when the JSON input does not have a structure that
  permits the request to be satisfied.  Back-patch to 9.4.  Update the
  release notes to list this as a behavior change since 9.3.
  http://git.postgresql.org/pg/commitdiff/41dd50e84df39e31595f3472b0cb6d00f63b3f99

- Fix another ancient memory-leak bug in relcache.c.
  CheckConstraintFetch() leaked a cstring in the caller's context for
  each CHECK constraint expression it copied into the relcache.
  Ordinarily that isn't problematic, but it can be during
  CLOBBER_CACHE testing because so many reloads can happen during a
  single query; so complicate the code slightly to allow freeing the
  cstring after use.  Per testing on buildfarm member barnacle.  This
  is exactly like the leak fixed in AttrDefaultFetch() by commit
  078b2ed291c758e7125d72c3a235f128d40a232b.  (Yes, this time I did
  look for other instances of the same coding pattern :-(.)  Like that
  patch, no back-patch, since it seems unlikely that there's any
  problem except under very artificial test conditions.  BTW, it
  strikes me that both of these places would require further work
  comparable to commit ab8c84db2f7af008151b848cf1d6a4672a39eecd, if we
  ever supported defaults or check constraints on system catalogs:
  they both assume they are copying into an empty relcache data
  structure, and that conceivably wouldn't be the case during
  recursive reloading of a system catalog.  This does not seem worth
  worrying about for the moment, since there is no near-term prospect
  of supporting any such thing.  So I'll just note the possibility for
  the archives' sake.
  http://git.postgresql.org/pg/commitdiff/73eba19aebe0101837668e39267469ca34373552

Heikki Linnakangas pushed:

- Reorganize functions in be-secure-openssl.c.  Move the functions
  within the file so that public interface functions come first,
  followed by internal functions. Previously, be_tls_write was first,
  then internal stuff, and finally the rest of the public interface,
  which clearly didn't make much sense.  Per Andres Freund's
  complaint.
  http://git.postgresql.org/pg/commitdiff/48d50840d53eb62842c0d9b54eab9cd7c9a3a46d

- Use comma+space as the separator in the default search_path.  While
  the space is optional, it seems nicer to be consistent with what you
  get if you do "SET search_path=...". SET always normalizes the
  separator to be comma+space.  Christoph Martin
  http://git.postgresql.org/pg/commitdiff/02587dcddc2cb5d9f7a17cb0281d168f5a0d6297

- Add #define INT64_MODIFIER for the printf length modifier for 64-bit
  ints.  We have had INT64_FORMAT and UINT64_FORMAT for a long time,
  but that's not good enough if you want something more exotic, like
  "%20lld".  Abhijit Menon-Sen, per Andres Freund's suggestion.
  http://git.postgresql.org/pg/commitdiff/ce486056ecd28050f367894a2b5aad3656d37511

- Change the way pg_basebackup's tablespace mapping is implemented.
  Previously, we would first create the symlinks the way they are in
  the original system, and at the end replace them with the mapped
  symlinks.  That never really made much sense, so now we create the
  symlink pointing to the correct location to begin with, so that
  there's no need to fix them at the end.  The old coding didn't work
  correctly on Windows, because Windows junction points look more like
  directories than files, and ought to be removed with rmdir rather
  than unlink. Also, it incorrectly used "%d" rather than "%u" to
  print an Oid, but that's gone now.  Report and patch by Amit Kapila,
  with minor changes by me. Reviewed by MauMau. Backpatch to 9.4,
  where the --tablespace feature was added.
  http://git.postgresql.org/pg/commitdiff/8d938eb0797e7acd925a2adf72315f8ab1586d83

- Fix comment in pg_basebackup.  The option is called
  --tablespace-mapping, not --tablespace.  Amit Kapila
  http://git.postgresql.org/pg/commitdiff/2af93640ad14028297fbc750e4c2338ad11a3c58

Gregory Stark pushed:

- Fix further concerns about psql wrapping in expanded mode having
  collateral damage on other formats, by Sergey Muraviov.
  http://git.postgresql.org/pg/commitdiff/458ef6bad15702a3ac9b7b302a0378f8817620c0

- Adjust Release Notes to reflect holding off wrapped expanded mode
  until 9.5 (thanks Michael Paquier)
  http://git.postgresql.org/pg/commitdiff/663675885ec2c97c8b59ce3e30f6ad05d162a584

Noah Misch pushed:

- Replace a few strncmp() calls with strlcpy().  strncmp() is a
  specialized API unsuited for routine copying into fixed-size
  buffers.  On a system where the length of a single filename can
  exceed MAXPGPATH, the pg_archivecleanup change prevents a simple
  crash in the subsequent strlen().  Few filesystems support names
  that long, and calling pg_archivecleanup with untrusted input is
  still not a credible use case.  Therefore, no back-patch.  David
  Rowley
  http://git.postgresql.org/pg/commitdiff/fb2aece8ae4e6f23310d7c87c7da3fec6f5df3a1

- Install libpq DLL with $(INSTALL_SHLIB).  Programs need execute
  permission on a DLL file to load it.  MSYS "install" ignores the
  mode argument, and our Cygwin build statically links libpq into
  programs.  That explains the lack of buildfarm trouble.  Back-patch
  to 9.0 (all supported versions).
  http://git.postgresql.org/pg/commitdiff/8605bc75219fd9a46fbb38909f83bcdae56b6e01

- Make pg_service.conf sample LDIF more portable.  The aboriginal
  sample placed connection parameters in
  groupOfUniqueNames/uniqueMember.  OpenLDAP, at least as early as
  version 2.4.23, rejects uniqueMember entries that do not conform to
  the syntax for a distinguished name.  Use device/description, which
  is free-form.  Back-patch to 9.4 for web site visibility.
  http://git.postgresql.org/pg/commitdiff/7fc5f1a3550ca9395051b592df150de79804131a

- Document new trigger-related forms of ALTER FOREIGN TABLE.
  Oversight in commit 7cbe57c34dec4860243e6d0f81738cfbb6e5d069.
  Back-patch to 9.4, where that commit first appeared.  In passing,
  release-note the FDW API postcondition change from the same commit.
  http://git.postgresql.org/pg/commitdiff/10718612fb23a5853e56eb792a6b1503ebddf190

- Finish adding file version information to installed Windows
  binaries.  In support of this, have the MSVC build follow GNU make
  in preferring GNUmakefile over Makefile when a directory contains
  both.  Michael Paquier, reviewed by MauMau.
  http://git.postgresql.org/pg/commitdiff/ee9569e4df1c3bdb6858f4f65d0770783c32a84d

Fujii Masao pushed:

- Fix bug in checking of IDENTIFY_SYSTEM result.
  5a991ef8692ed0d170b44958a81a6bd70e90585 added new column into the
  result of IDENTIFY_SYSTEM command. But it was not reflected into
  several codes checking that result. Specifically though the number
  of columns in the result was increased to 4, it was still compared
  with 3 in some replication codes.  Back-patch to 9.4 where the
  number of columns in IDENTIFY_SYSTEM result was increased.  Report
  from Michael Paquier
  http://git.postgresql.org/pg/commitdiff/083d29c65b7897f90c70e6dc0a4240a5fa75c8f2

- Revert "Fix bug in checking of IDENTIFY_SYSTEM result." This reverts
  commit 083d29c65b7897f90c70e6dc0a4240a5fa75c8f2.  The commit changed
  the code so that it causes an errors when IDENTIFY_SYSTEM returns
  three columns. But which prevents us from using the
  replication-related utilities against the server with older version.
  This is not what we want. For that compatibility, we allow the
  utilities to receive three columns as the result of IDENTIFY_SYSTEM
  eventhough it actually returns four columns in 9.4 or later.
  Pointed out by Andres Freund.
  http://git.postgresql.org/pg/commitdiff/c4762886539b06da682045e19ba73dcee3789638

Bruce Momjian pushed:

- pg_upgrade:  adjust logging to use QUERY_ALLOC lengths.  Allows the
  logging to print the entire text of failed queries, rather than a
  truncated version.
  http://git.postgresql.org/pg/commitdiff/7567d94910c100a28a79122e86297cd7a4c90df6

Stephen Frost pushed:

- Rework 'MOVE ALL' to 'ALTER .. ALL IN TABLESPACE'.  As 'ALTER
  TABLESPACE .. MOVE ALL' really didn't change the tablespace but
  instead changed objects inside tablespaces, it made sense to rework
  the syntax and supporting functions to operate under the 'ALTER
  (TABLE|INDEX|MATERIALIZED VIEW)' syntax and to be in tablecmds.c.
  Pointed out by Alvaro, who also suggested the new syntax.
  Back-patch to 9.4.
  http://git.postgresql.org/pg/commitdiff/3c4cf080879b386d4ed1814667aca025caafe608

Andres Freund pushed:

- Add pinning_backends column to the pg_buffercache extension.  The
  new column shows how many backends have a buffer pinned. That can be
  useful during development or to diagnose production issues e.g.
  caused by vacuum waiting for cleanup locks.  To handle upgrades
  transparently - the extension might be used in views - deal with
  callers expecting the old number of columns.  Reviewed by Fujii
  Masao and Rajeev rastogi.
  http://git.postgresql.org/pg/commitdiff/f57791985ac3d776cb67e9d69befde538cfdf13b

- Fix newly introduced misspelling of existence in pg_buffercache.
  Peter Geoghegan
  http://git.postgresql.org/pg/commitdiff/ebf20f65d9383166d4b883258c091b245cf36217

Peter Eisentraut pushed:

- Fix whitespace
  http://git.postgresql.org/pg/commitdiff/3feda1bcbb653e954092bddd9c3eb681ab51fa2b

- doc: Improve pg_restore help output.  Add a note that some options
  can be specified multiple times to select multiple objects to
  restore.  This replaces the somewhat confusing use of plurals in the
  option descriptions themselves.
  http://git.postgresql.org/pg/commitdiff/256bfb2c9ab89eefb963db025dfcc91893f0b8b3

Alvaro Herrera pushed:

- Fix outdated comment
  http://git.postgresql.org/pg/commitdiff/01d15a2677c738489e62295924298ef8a72528a8

- Implement ALTER TABLE .. SET LOGGED / UNLOGGED.  This enables
  changing permanent (logged) tables to unlogged and vice-versa.
  (Docs for ALTER TABLE / SET TABLESPACE got shuffled in an order that
  hopefully makes more sense than the original.) Author: Fabrízio de
  Royes Mello Reviewed by: Christoph Berg, Andres Freund, Thom Brown
  Some tweaking by Álvaro Herrera
  http://git.postgresql.org/pg/commitdiff/f41872d0c1239d36ab03393c39ec0b70e9ee2a3c

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Anastasia Lubennikova and Heikki Linnakangas traded patches to enable
index-only scans for GiST.

Fujii Masao and Michael Paquier traded patches to fix an issue with
pg_receivexlog and replication slots.

Adam Brightwell sent in another revision of a patch to implement
row-level access control.

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

Adam Brightwell sent in a PoC patch to create a new model around role
attributes and fine grained permissions meant to alleviate the current
over-dependence on superuser.

Furuya Osamu sent in two more revisions of a patch to add fsync
feedback to pg_receivexlog --status-interval.

David Rowley sent in another revision of a patch to implement partial
sorting.

Rahila Syed sent in another revision of a patch to compress full-page
writes.

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

Vladislav Sterzhanov sent in a patch to enable KNN searches for
SP-GiST.

Michael Paquier and Fabrízio de Royes Mello traded patches to ensure
that the verbose output of pg_dump show the schema name.

Jeff Davis and Tomas Vondra traded patches to do better memory
accounting for hash aggregates.

John Lumby sent in a patch to extend prefetching using asynchronous
I/O.

Amit Kapila sent in another revision of a patch to fix pg_basebackup
with respect to tablespaces on Windows.

Alvaro Herrera sent in two more revisions of a patch to implement
minmax indexes.

Andreas 'ads' Scherbaum sent in a patch to explains that functions
like round() and others might behave differently depending on
operating system, and that this is correct according to an IEEE
standard.

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

Fabrízio de Royes Mello, Alvaro Herrera, and Michael Paquier traded
patches to implement ALTER TABLE ... SET LOGGED.

Tom Lane sent in a patch to make JSONB more TOAST-compressible.

Julien Rouhaud sent in a patch to track number of files ready to be
archived in pg_stat_archiver.

Bruce Momjian sent in a patch to update recommendations around pg_dump
to reflect current capabilities.

Bruce Momjian sent in a patch to harden pg_upgrade.

Amit Kapila sent in two more revisions of a patch to fix an issue
where the -T option of pg_basebackup didn't work on Windows.

Bruce Momjian sent in a patch to allow multiple -o/-O options in
pg_upgrade.

Kevin Grittner sent in another revision of a patch to enable delta
relations in AFTER triggers.

Peter Geoghegan sent in another revision of a patch to add a b-tree
sort support optimization.

Pavel Stehule sent in another revision of a patch to revamp
row_to_json.

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

Jov and Tom Lane traded patches to change alter user to be a true
alias for alter role.

Tomonari Katsumata sent in a patch to allow rounding up time value
less than its unit.

Alvaro Herrera and Thomas Munro traded patches to add SKIP LOCKED
DATA.

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

Michael Paquier sent in a patch to add a missing comment block at the
top of streamutil.h and receivelog.h.

Fabien COELHO sent in another revision of a patch to create a pgbench
throttling latency limit.

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

Amit Kapila sent in another revision of a patch to add ALTER SYSTEM
RESET.

--

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

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
Agile Business Group (www.agilebg.com), Jobrapido (www.jobrapido.com),
Navionics (www.navionics.com), and Subito.it (www.subito.it).

For a complete list of changes, see the "Release Notes" section
below.

Links

  * Website: http://www.pgbarman.org/
  * Download: http://sourceforge.net/projects/pgbarman/files/
  * Documentation: http://www.pgbarman.org/documentation/
  * Support: http://www.pgbarman.org/support/
  * pgespresso extension: https://github.com/2ndquadrant-it/pgespresso

Release notes

  * Added "last_backup_max_age", a new global/server option that
    allows administrators to set the max age of the last backup in a
    catalogue, making it easier to detect any issues with periodical
    backup execution
  * Improved robustness of "barman backup" by introducing two global/
    server options: "basebackup_retry_times" and
    "basebackup_retry_sleep". These options allow an administrator to
    specify, respectively, the number of attempts for a copy
    operation after a failure, and the number of seconds of wait
    before retrying
  * Improved the recovery process via rsync on an existing directory
    (incremental recovery), by splitting the previous rsync call into
    several ones - invoking checksum control only when necessary
  * Added support for PostgreSQL 8.3
  * Minor changes:

      + Support for comma separated list values configuration options
      + Improved backup durability by calling fsync() on backup and
        WAL files during "barman backup" and "barman cron"
      + Improved Nagios output for "barman check --nagios"
      + Display compression ratio for WALs in "barman show-backup"
      + Correctly handled keyboard interruption (CTRL-C) while
        performing barman backup
      + Improved error messages of failures regarding the stop of a
        backup
      + Wider coverage of unit tests
  * Bug fixes:

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

Download

  * Release Notes: https://sourceforge.net/projects/pgbarman/files/1.3.3/
  * Sources: http://sourceforge.net/projects/pgbarman/files/1.3.3/barman-1.3.3.tar.gz/download
  * RPMs for RHEL/CentOS 5:
http://sourceforge.net/projects/pgbarman/files/1.3.3/barman-1.3.3-1.rhel5.noarch.rpm/download
    (dependencies: https://sourceforge.net/projects/pgbarman/files/rhel5-deps/)
  * RPMs for RHEL/CentOS 6:
http://sourceforge.net/projects/pgbarman/files/1.3.3/barman-1.3.3-1.rhel6.noarch.rpm/download
    (dependencies: https://sourceforge.net/projects/pgbarman/files/rhel6-deps/)
  * PyPI: http://pypi.python.org/pypi/barman/1.3.3
  * pgespresso on PostgreSQL Extension framework (PGXN):
http://pgxn.org/dist/pgespresso/
  * pgespresso RPM/Debian packages:
https://sourceforge.net/projects/pgbarman/files/pgespresso/
  * Online documentation: http://www.pgbarman.org/documentation
  * PDF documentation:
http://sourceforge.net/projects/pgbarman/files/1.3.3/barman-tutorial.en.pdf/download

Barman (Backup and Recovery Manager) is an open source administration
tool for disaster recovery of PostgreSQL servers written in Python.
It allows your organisation to perform remote backups of multiple
servers in business critical environments and help DBAs during the
recovery phase. Barman’s most requested features include backup
catalogues, retention policies, remote backup and recovery, archiving
and compression of WAL files and backups. Barman is distributed under
GNU GPL 3.

--
 Gabriele Bartolini - 2ndQuadrant Italia
 PostgreSQL Training, Services and Support
 gabriele.bartolini <at> 2ndQuadrant.it | www.2ndQuadrant.it

--

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


Gmane