Virginie Jourdan | 20 Apr 12:21 2015

Call for Papers, PostgreSQL Session #7, September, 24th

Paris, April 20th 2015

After six successful sessions dedicated to the new features of PostgreSQL 9.0 (February 2011), to PostGIS (June 2011 & September 2014), to replication systems (February 2012), to migration from Oracle to PostgreSQL (October 2012), and to PostgreSQL performance (March 2013), we'd like to announce that the 7th PostgreSQL Session will be held on September 24th, 2015, in Paris, France.

This year, another place, but always the same format! This day of lectures will be dedicated especially to the next version of PostgreSQL, but not exclusively!

For more information, see http://www.postgresql-sessions.org/7/about

We're launching a call for papers for this event. You may now submit your talks, in English or in French. Each talk should last 30 minutes (questions included). We are interested in any talks on the following subjects:

  * What's New in PostgreSQL
  * Use cases
  * Migration to PostgreSQL
  * Performance Tuning
  * Backup and Restore
  * High-Availibity
  * Data Warehouse / Big Data
  * PostGIS

Talks can be either: a case study, a Proof of Concept, a tutorial, a benchmark, a presentation of a new feature, etc. Of course, we're open to propositions on any other migration related topics (monitoring, hardware, replication, etc.) !

The submission deadline is June 15, 2015.

You can now send your proposals to call-for-paper <at> postgresql-sessions.org

Please give us a little information about yourself and your talk, such as:

  * First Name and Last Name
  * Twitter Account (if any)
  * Company
  * Short Biography (contributions to the PostgreSQL community)
  * Talk title
  * Talk abstract
  * Any specific needs

Slides should have a free licence (Creative Commons BY-ND 3.0 or compatible), and sent to Dalibo.

This day will be filmed, and all the lectures will be recorded and published after the Session. By sending a proposal, you agree to be recorded and waive any compensation for it.

The selected speakers not living in France will be reimbursed for travel and one night accomodation.

See you in Paris in September!

About the PostgreSQL Sessions

The PostgreSQL sessions are designed to be a time to discover and meet the PostgreSQL community. Each session is a single day consisting of lectures, organized around a specific theme and a guest. The proposed talks aimed at all levels and all profiles: Developer, Administrator, Project Managers, IT Managers, ...
Entry is free and open to all, within the limits of available seats.

About Dalibo

Since 2005, Dalibo is the leading French PostgreSQL company and provides its experience and expertise to its clients in Europe. The company
delivers a full range of PostgreSQL services: Training, Development, Performance Tuning, High Availibilty setup, Oracle to
PostgreSQL migration, Troubleshooting, and PostgreSQL support.
David Fetter | 20 Apr 01:25 2015

== PostgreSQL Weekly News - April 19 2015 ==

== PostgreSQL Weekly News - April 19 2015 ==

== PostgreSQL Product News ==

Ora2PG 15.2, a migration system for moving from Oracle to PostgreSQL, released.
http://ora2pg.darold.net/

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

pgFormatter v1.4, a SQL formatter/beautifier which supports keywords
from SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011 and PostgreSQL
keywords are not in the standard, released.
http://sqlformat.darold.net/

pg_monz v2.0, a Zabbix template for monitoring PostgreSQL, released.
http://pg-monz.github.io/pg_monz/index-en.html

== PostgreSQL Jobs for April ==

http://archives.postgresql.org/pgsql-jobs/2015-04/threads.php

== PostgreSQL Local ==

The 4th Turkish PostgreSQL Conference will be held on May 9, 2015 in
Istanbul.
http://pgday.postgresql.org.tr/en/index.html

The second Swiss Postgres Conference will be held June 25-26, 2015 at
HSR Rapperswil.
http://www.postgres-conference.ch/

There is a Postgres track in a database technology conference(DTCC) in
April 18, 2015 in Beijing, China.
http://dtcc.it168.com/list_jiabin.html

pgDay Paris will be held in Paris France on April 21, 2015.
http://pgday.paris/

Call for Papers for PGDay in Belfort, France ends April 13, 2015.
The conference will be held June 2, 2015.
http://select-2-6-2015-as-pgday.org

PGCon 2015 is June 16-20 in Ottawa, Canada.
http://www.pgcon.org/2015/

PGDay UK, Conference will be taking place on 7th July 2015 – it is aimed at
the UK PostgreSQL Community.  The CfP is open until 13 April 2015.
http://www.postgresqlusergroup.org.uk

The Call For Papers for PostgresOpen 2015, being held in Dallas, Texas
from September 16th to 18th, is now open.
http://2015.postgresopen.org/callforpapers/

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

- emacs: Set indent-tabs-mode in perl-mode This matches existing
  practice, but makes the setup complete and consistent with the C
  code setup.
  http://git.postgresql.org/pg/commitdiff/442663f133f1caec51919402463e6e31362baee3

- Move pgbench from contrib/ to src/bin/.  Reviewed-by: Michael
  Paquier <michael.paquier <at> gmail.com>
  http://git.postgresql.org/pg/commitdiff/81134af3ec09d67043833f8d614fd688f17cb213

- pgbench: Attempt fix build on Windows
  http://git.postgresql.org/pg/commitdiff/d577bb868dfb595aa8df95974cd1c79e1baba924

- Move pg_upgrade from contrib/ to src/bin/.  Reviewed-by: Michael
  Paquier <michael.paquier <at> gmail.com>
  http://git.postgresql.org/pg/commitdiff/9fa8b0ee90c44c0f97d16bf65e94322988c94864

- Integrate pg_upgrade_support module into backend.  Previously, these
  functions were created in a schema "binary_upgrade", which was
  deleted after pg_upgrade was finished.  Because we don't want to
  keep that schema around permanently, move them to pg_catalog but
  rename them with a binary_upgrade_... prefix.  The provided
  functions are only small wrappers around global variables that were
  added specifically for pg_upgrade use, so keeping the module
  separate does not create any modularity.  The functions still check
  that they are only called in binary upgrade mode, so it is not
  possible to call these during normal operation.  Reviewed-by:
  Michael Paquier <michael.paquier <at> gmail.com>
  http://git.postgresql.org/pg/commitdiff/30982be4e5019684e1772dd9170aaa53f5a8e894

Fujii Masao pushed:

- Silence gettext warning about '\r' escape sequence in translatable
  string.  gettext was unhappy about the commit b216ad7 because it
  revealed the problem that internationalized messages may contain
  '\r' escape sequence in pg_rewind. This commit moves '\r' to a
  separate printf() call.  Michael Paquier, bug reported by Peter
  Eisentraut
  http://git.postgresql.org/pg/commitdiff/1f94bec7a9e3e6b4fa5468236cf531fec16d1093

Heikki Linnakangas pushed:

- Refactor and fix TAP tests of pg_rewind * Don't pass arguments to
  prove, since that's not supported on perl 5.8 which is the minimum
  version supported by the TAP tests. Refactor the test files
  themselves to run the tests twice, in both local and remote mode.  *
  Use eq rather than == for string comparison. This thinko caused the
  remote versions of the tests to never run.  * Add "use strict" and
  "use warnings", and fix warnings that that produced.  * Increase the
  delay after standby promotion, to make the tests more robust.  * In
  remote mode, the connection string to the promoted standby was
  incorrect, leading to connection errors.  Patch by Michael Paquier,
  to address Peter Eisentraut's report.
  http://git.postgresql.org/pg/commitdiff/53ba10770a315361770efdc17d2c01f6a30e3e3d

- Fix pg_rewind regression tests in VPATH builds.  Should call just
  "pg_rewind", instead of "./pg_rewind". The tests are called so that
  PATH contains the temporariy installation bin dir.  Per report from
  Alvaro Herrera
  http://git.postgresql.org/pg/commitdiff/b22a36a62ce312c1df9477382d1da602b0c24f6f

- Reorganize our CRC source files again.  Now that we use CRC-32C in
  WAL and the control file, the "traditional" and "legacy" CRC-32
  variants are not used in any frontend programs anymore.  Move the
  code for those back from src/common to src/backend/utils/hash.  Also
  move the slicing-by-8 implementation (back) to src/port. This is in
  preparation for next patch that will add another implementation that
  uses Intel SSE 4.2 instructions to calculate CRC-32C, where
  available.
  http://git.postgresql.org/pg/commitdiff/4f700bcd20c087f60346cb8aefd0e269be8e2157

- Don't archive bogus recycled or preallocated files after timeline
  switch.  After a timeline switch, we would leave behind recycled WAL
  segments that are in the future, but on the old timeline. After
  promotion, and after they become old enough to be recycled again, we
  would notice that they don't have a .ready or .done file, create a
  .ready file for them, and archive them.  That's bogus, because the
  files contain garbage, recycled from an older timeline (or
  prealloced as zeros). We shouldn't archive such files.  This could
  happen when we're following a timeline switch during replay, or when
  we switch to new timeline at end-of-recovery.  To fix, whenever we
  switch to a new timeline, scan the data directory for WAL segments
  on the old timeline, but with a higher segment number, and remove
  them. Those don't belong to our timeline history, and are most
  likely bogus recycled or preallocated files. They could also be
  valid files that we streamed from the primary ahead of time, but in
  any case, they're not needed to recover to the new timeline.
  http://git.postgresql.org/pg/commitdiff/b2a5545bd63fc94a71b1e97ecdd03c605d97a438

- Use Intel SSE 4.2 CRC instructions where available.  Modern x86 and
  x86-64 processors with SSE 4.2 support have special instructions,
  crc32b and crc32q, for calculating CRC-32C. They greatly speed up
  CRC calculation.  Whether the instructions can be used or not
  depends on the compiler and the target architecture. If generation
  of SSE 4.2 instructions is allowed for the target (-msse4.2 flag on
  gcc and clang), use them. If they are not allowed by default, but
  the compiler supports the -msse4.2 flag to enable them, compile just
  the CRC-32C function with -msse4.2 flag, and check at runtime
  whether the processor we're running on supports it. If it doesn't,
  fall back to the slicing-by-8 algorithm. (With the common defaults
  on current operating systems, the runtime-check variant is what you
  get in practice.) Abhijit Menon-Sen, heavily modified by me,
  reviewed by Andres Freund.
  http://git.postgresql.org/pg/commitdiff/3dc2d62d0486325bf263655c2d9a96aee0b02abe

- Try to fix the CRC-32C autoconf magic for icc compiler.  On gcc and
  clang, the _mm_crc32_u8 and _mm_crc32_u64 intrinsics are not defined
  at all, when not building with -msse4.2. But on icc, they are.  So
  we cannot assume that if those intrinsics are defined, we can always
  use them safely, we might still need the runtime check.  To fix,
  check if the __SSE_4_2__ preprocessor symbol is defined. That's
  supposed to be defined only when the compiler is targeting a
  processor that has SSE 4.2 support.  Per buildfarm members fulmar
  and okapi.
  http://git.postgresql.org/pg/commitdiff/b4eb2d168d2c426978a02de8b9b6ccdb85e1b442

- Oops, fix misspelled #endif.  I hope this fixes the Windows builfarm
  failures.
  http://git.postgresql.org/pg/commitdiff/b73e7a0716264e5159947b1a755b9ab864142489

- Optimize pg_comp_crc32c_sse42 routine slightly, and also use it on
  x86.  Eliminate the separate 'len' variable from the loops, and also
  use the 4 byte instruction. This shaves off a few more cycles. Even
  though this routine that uses the special SSE 4.2 instructions is
  much faster than a generic routine, it's still a hot spot, so let's
  make it as fast as possible.  Change the configure test to not test
  _mm_crc32_u64. That variant is only available in the 64-bit x86-64
  architecture, not in 32-bit x86. Modify pg_comp_crc32c_sse42 so that
  it only uses _mm_crc32_u64 on x86-64. With these changes, the SSE
  accelerated CRC-32C implementation can also be used on 32-bit x86
  systems.  This also fixes the 32-bit MSVC build.
  http://git.postgresql.org/pg/commitdiff/936546dcbc24ad1f2b3d33e73aa5c5fde4d2be84

- Fix logic to skip checkpoint if no records have been inserted.
  After the WAL format changes, the calculation of the size of a
  checkpoint record became incorrect. Instead of trying to fix the
  math, check that the previous record, i.e. the xl_prev value that
  we'd write for the next record, matches the last checkpoint's redo
  pointer. That way it's not dependent on the size of the checkpoint
  record at all.  The old logic was actually slightly wrong all along:
  if the previous checkpoint record crossed a page boundary, the page
  headers threw off the record size calculation, and the checkpoint
  was not skipped. The new checkpoint would not cross a page boundary,
  so this only resulted in at most one extra checkpoint after the
  system became idle. The new logic fixes that. (It's not worth fixing
  in backbranches).  However, it makes some sense to try to keep the
  latest checkpoint contained fully in a page, or at least in a single
  WAL segment, just on general robustness grounds. If something goes
  awfully wrong, it's more likely that you can recover the latest WAL
  segment, than the last two WAL segments. So I added an extra check
  that the checkpoint is not skipped if the previous checkpoint
  crossed a WAL segment.  Reported by Jeff Janes.
  http://git.postgresql.org/pg/commitdiff/3d80a1e0e3e278edc6022d642478dcbd089d4483

- Shut down test servers after pg_rewind regression tests.  Now that
  the test servers are initialized twice in each .pl script, the
  single END block is not enough to stop them. Add a new
  clean_rewind_test function that is called at the end of each test.
  Michael Paquier
  http://git.postgresql.org/pg/commitdiff/0d8a22a9ac6a61b7993abb642cb7e4645f4087b0

- Minor cleanup of pg_rewind.  Update comments and function names to
  use the terms "source" and "target" consistently. Some places were
  calling them remote and local instead, which was confusing.  Fix
  incorrect comment in extractPageInfo on database creation record -
  it was wrong on what happens for databases created in the target
  that don't exist in source.
  http://git.postgresql.org/pg/commitdiff/41457fcf970f0ec78004cc0f7b29f1d37021fbfb

- Add missing newlines to error messages.
  http://git.postgresql.org/pg/commitdiff/b5e384e374657ead815a3393ca59333910611a24

- Error out in pg_rewind if lstat() fails.  A "file not found" is
  expected if the source server is running, so don't complain about
  that. But any other error is definitely not expected.
  http://git.postgresql.org/pg/commitdiff/b5e560c24603e5325a81055c8f36cc45d48609e4

- Fix assertion failure in logical decoding.  Logical decoding set
  SnapshotData's regd_count field to avoid the snapshot manager from
  prematurely freeing snapshots that are generated by the decoding
  system. That was always an abuse of the field, as it was never
  supposed to be used outside the snapshot manager. Commit 94028691
  made snapshot manager's tracking of the snapshots smarter, and that
  scheme fell apart. The snapshot manager got confused and hit the
  assertion, when a snapshot that was marked with regd_count==1 was
  not found in the heap, where the snapshot manager tracks registered
  the snapshots.  To fix, don't abuse the regd_count field like that.
  Logical decoding still abuses the active_count field for similar
  purposes, but that's currently harmless.  The assertion failure was
  first reported by Michael Paquier
  http://git.postgresql.org/pg/commitdiff/e2999abcd14540e66b72deeff75662c1672d7744

Álvaro Herrera pushed:

- Remove duplicated word in README
  http://git.postgresql.org/pg/commitdiff/b5213e14a4759b8f6817359c827950bae5452136

- Fix typo in comment.  SLRU_SEGMENTS_PER_PAGE ->
  SLRU_PAGES_PER_SEGMENT I introduced this ancient typo in subtrans.c
  and later propagated it to multixact.c.  I fixed the latter in
  f741300c, but only back to 9.3; backpatch to all supported branches
  for consistency.
  http://git.postgresql.org/pg/commitdiff/0a52fafce42e47d151d1108a44b25152a908c732

- MSVC: Include modules of src/test/modules in build.  commit_ts,
  being only a module used for test purposes, is ignored in the
  process for now.  Author: Michael Paquier Reviewed by: Andrew
  Dunstan
  http://git.postgresql.org/pg/commitdiff/90898af30bb287a512bef743253770fc24886da6

- MSVC: install src/test/modules together with contrib.  These modules
  have to be installed so that the testing module can access them.
  (We don't have that yet, but will soon have it.) Author: Michael
  Paquier.  Reviewed by: Andrew Dunstan
  http://git.postgresql.org/pg/commitdiff/22d005323f917d0189bcee8e6cbbbcf5906b2358

- Add new target modulescheck in vcregress.pl.  This allows an MSVC
  build to run regression tests related to modules in
  src/test/modules.  Author: Michael Paquier Reviewed by: Andrew
  Dunstan
  http://git.postgresql.org/pg/commitdiff/4cb7d671fddc8855c8def2de51fb23df1c8ac0af

Bruce Momjian pushed:

- pg_upgrade:  document need for text search files to be copied.
  Report by CJ Estel.  Backpatch through 9.4
  http://git.postgresql.org/pg/commitdiff/2e5d52a644a4cad9f37a1b2a1e61be8eb631b901

- pg_upgrade:  binary_upgrade_create_empty_extension() is strict.  Was
  broken by commit 30982be4e5019684e1772dd9170aaa53f5a8e894.  Patch by
  Jeff Janes
  http://git.postgresql.org/pg/commitdiff/f92fc4c95ddcc25978354a8248d3df22269201bc

Stephen Frost pushed:

- Fix typo in relcache's equalPolicy().  The USING policies were not
  being checked for differences as the same policy was being passed in
  to both sides of the equal().  This could result in backends not
  realizing that a policy had been changed, if none of the other
  attributes had been changed.  Fix by passing to equal() the policy1
  and policy2 using quals for comparison.  No need to back-patch as
  this is not yet released.  Noticed while testing changes to RLS
  proposed by Dean Rasheed.
  http://git.postgresql.org/pg/commitdiff/ab6d1cd26ebfbfce275cd31af82814c0620e70a2

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Stephen Frost sent in another revision of a patch to use GRANT for
access to privileged functions.

Etsuro Fujita sent in two more revisions of a patch to fix some
oddities with EvalQualPlan for FDW queries involving system columns.

David Steele sent in three more revisions of a patch to implement
pg_audit.

Simon Riggs sent in another revision of a patch to disable HOT
cleanup, sometimes.

Etsuro Fujita sent in another revision of a patch to fix some
infelicities in the new feature of having foreign tables in
inheritance trees.

Etsuro Fujita sent in a patch to allow WITH OIDs when issuing CREATE
FOREIGN TABLE, making it consistently able with ALTER FOREIGN TABLE.

Peter Geoghegan sent in another revision of a patch to implement
INSERT ... ON CONFLICT IGNORE (and UPDATE).

Zhang Zq sent in a patch to fix an issue where duplicate checkpoints
were being inserted when the system was idle.

Qingqing Zhou sent in a patch to assert there is no duplicated exit
callbacks.

Qingqing Zhou sent in a patch to use outerPlanState() consistently in
the executor code.

Álvaro Herrera sent in a patch to show xl_prev in xlog.c errcontext.

J.L. Tallon sent in a patch to implement a new GUC
(default_index_tablespace) plus supporting code.

Michael Paquier sent in a doc patch to warn about possible information
leakage from compressing full-page writes.

Etsuro Fujita sent in a patch to fix some markup in config.sgml.

Abhijit Menon-Sen sent in another revision of a patch to recursively
fsync PGDATA at startup if needed.

Michael Paquier sent in a patch to fix broken Install.bat when target
directory contains a space.

Shigeru HANADA sent in two more revisions of a patch to add custom and
foreign JOIN APIs.

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

Zhang Zq sent in a patch to implement xidin.

Abhijit Menon-Sen sent in a patch to avoid dividing by zero when
calculating percentages.

Andres Freund sent in another revision of a patch to iIntroduce
replication identifiers.

Petr Jelinek sent in another revision of a patch to implement
TABLESAMPLE.

Dmitry Dolgov sent in another revision of a patch to add some useful
functions for manipulating and pretty-printing JSON.

Michael Paquier sent in a patch to add a missing --debug for remote
mode in pg_rewind tests to RewindTest.pm.

Michael Paquier sent in another revision of a patch to add support for
TAP tests on Windows and prefer IPC's run to system_or_bail in
pg_rewind tests.

Mikko Tiihonen sent in a patch to libpq which allows specifying
multiple host names to try to connect to.

Tomas Vondra sent in a patch to allow initdb-time support for various
compression algorithms.

--

-- 
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 | 19 Apr 18:16 2015

pgFormatter 1.4

pgFormatter 1.4 released
----------------------------------

Version 1.4 of pgFormatter, a free a SQL formatter/beautifier dedicated
to standard SQL and PostgreSQL specifics keywords, has been officially
released and is publicly available for download.

This release fixes several issues and adds a useful anonymization option to
be able to obfuscate all values in SQL queries. See option -a | --anonymize
at command line or the corresponding checkbox in the CGI interface.

For the full list of changes, see:

    Changelog: https://github.com/darold/pgFormatter/blob/master/ChangeLog

Links & Credits
--------------------

Thank to the developers who submitted patches and users who reported bugs
and feature requests, especially Alvaro Herrera, Hubert depesz Lubaczewski,
David Fetter and rimbault.

pgFormatter 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.

Links:

    Website: http://sqlformat.darold.net/
    Download: http://sourceforge.net/projects/pgformatter/
    Development: https://github.com/darold/pgFormatter

About pgFormatter
-------------------------

pgFormatter is a SQL formatter/beautifier that supports keywords from
SQL-92, SQL-99, SQL-2003, SQL-2008, SQL-2011 and PostgreSQL specifics
keywords. May works with any other databases too. It shares the same
code with pgBadger, so any improvement made in the parser is reversed to
pgBadger. Tool created by Gilles Darold.

pgFormatter can work as a console program or as a CGI. It will
automatically detect his environment and output as text or as HTML
following the context.

pgFormatter works on any platform and is available under the PostgreSQL
licence.

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

Yoshiharu Mori | 16 Apr 08:34 2015
Picon

pg_monz v2.0 is out

PostgreSQL monitoring template for Zabbix (pg_monz v2.0) 
has been released. You can get it from:

http://pg-monz.github.io/pg_monz/index-en.html

pg_monz v2.0 enables various types of monitoring of PostgreSQL 
such as alive, resource, performance, etc. 
New version contains monitoring streaming replication and pgpool-II.

You can use pg_monz for auto-recovery at the time of PostgreSQL troubles, 
monitoring long-term changes in PostgreSQL system status, and so on.

pg_monz is distributed under the Apache License Version 2.0. If you
have questions and/or opinions, please contact to: pg_monz Users Group
pg_monz(at)googlegroups(dot)com(dot)

--
Yoshiharu Mori 

--

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

Charles Clavadetscher | 14 Apr 14:04 2015

2nd Swiss Postgres Conference

Hello

This year, as mentioned in a previous mail, there will be a Swiss PostgreSQL
Conference again, in June 2015. The program has been defined a few days ago
and registration is open. Until May 15th, 2015 you may profit of an early
bird rate.

http://www.postgres-conference.ch/

Besides the conference itself there will be a full workshop day. For the
workshops as well as for the conference talks we received commitments from
international well known experts on the topics treated. The odds are good
that the event will become highly interesting.

We would be very pleased to welcome you in Rapperswil.

Best regards

Charles Clavadetscher
OK Swiss Postgres Conference

Swiss PostgreSQL Users Group
http://www.swisspug.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

Gilles Darold | 13 Apr 18:28 2015

Ora2Pg 15.2 is out

Ora2Pg 15.2 released

Version 15.2 of Ora2Pg, a free and reliable tool used to migrate an
Oracle database to PostgreSQL, has been officially released and is
publicly available for download.

This new minor release fixes some issues and adds two new configuration
directives:

  * ORA_INITIAL_COMMAND to be able to execute a custom command just after
    the connection to Oracle, for example to unlock a security policy.
  * INTERNAL_DATE_MAX to change the behavior of Ora2Pg with internal date
    found in user defined types.

This version will also automatically re-order exported views taking into
account interdependencies.

As usual these also some bug fixes and Oracle to PostgreSQL conversion
adjustments, see https://github.com/darold/ora2pg/blob/master/changelog
for a complete list.

Thanks to all contributors, they are all cited in the changelog file.

Useful Links:

    - Website: http://ora2pg.darold.net/
    - Download: http://sourceforge.net/projects/ora2pg/
    - Development: https://github.com/darold/ora2pg
    - Changelog: https://github.com/darold/ora2pg/blob/master/changelog
    - Documentation: https://github.com/darold/ora2pg/blob/master/README

About Ora2Pg :

Ora2Pg is an easy and reliable tool to migrate from Oracle to PostgreSQL.
It is developed since 2001 and can export most of the Oracle objects
(table, view, materialized view, tablespace, sequence, indexes, trigger,
grant, function, procedure, package, partition, data, blob and external
table).

Ora2Pg works on any platform and is available under the GPL v3 licence.

Docs, Download & Support at http://ora2pg.darold.net/

-- 
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 | 13 Apr 02:28 2015

== PostgreSQL Weekly News - April 12 2015 ==

== PostgreSQL Weekly News - April 12 2015 ==

The 4th Turkish PostgreSQL Conference will be held on May 9, 2015 in
Istanbul.
http://pgday.postgresql.org.tr/en/index.html

== PostgreSQL Product News ==

pgbouncer 1.5.5, a light-weight connection pooler for PostgreSQL, released.
https://pgbouncer.github.io/downloads/

pgpool-II versions 3.4.2, 3.3.6, 3.2.11, 3.1.14, and 3.0.17 released.
pgpool-II is a connection pooler and replication system for PostgreSQL.
http://pgpool.net/mediawiki/index.php/Downloads

== PostgreSQL Jobs for April ==

http://archives.postgresql.org/pgsql-jobs/2015-04/threads.php

== PostgreSQL Local ==

The second Swiss Postgres Conference will be held June 25-26, 2015 at
HSR Rapperswil.
http://www.postgres-conference.ch/

There is a Postgres track in a database technology conference(DTCC) in
April 18, 2015 in Beijing, China.
http://dtcc.it168.com/list_jiabin.html

pgDay Paris will be held in Paris France on April 21, 2015.
http://pgday.paris/

Call for Papers for PGDay in Belfort, France ends April 13, 2015.
The conference will be held June 2, 2015.
http://select-2-6-2015-as-pgday.org

PGCon 2015 is June 16-20 in Ottawa, Canada.
http://www.pgcon.org/2015/

PGDay UK, Conference will be taking place on 7th July 2015 – it is aimed at
the UK PostgreSQL Community.  The CfP is open until 13 April 2015.
http://www.postgresqlusergroup.org.uk

The Call For Papers for PostgresOpen 2015, being held in Dallas, Texas
from September 16th to 18th, is now open.
http://2015.postgresopen.org/callforpapers/

== 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 typo in libpq.sgml.  Back-patch to all supported versions.
  Michael Paquier
  http://git.postgresql.org/pg/commitdiff/5f6a9d056a3ba8ba66cace5d84e46caadc6e3a42

- Add file_ops.c to GETTEXT_FILES in nls.mk.  Since file_ops.c
  contains translatable strings, it should have been listed in
  GETTEXT_FILES.
  http://git.postgresql.org/pg/commitdiff/29407f97746ba2543b1845afe8ae22af09d43e45

- Fix typo in comment.
  http://git.postgresql.org/pg/commitdiff/026fafde9159046ad26d0ccba92be0e802c70e92

- Remove obsolete FORCE option from REINDEX.  FORCE option has been
  marked "obsolete" since very old version 7.4 but existed for
  backwards compatibility. Per discussion on pgsql-hackers, we
  concluded that it's no longer worth keeping supporting the option.
  http://git.postgresql.org/pg/commitdiff/17d436d2e894a91f3e8a9eb1bb1688cb515f1546

- Mark the second argument of pg_log as the translatable string in
  nls.mk.
  http://git.postgresql.org/pg/commitdiff/b216ad7bf1a9308c97d2032d4793010e8c8aa7ec

Álvaro Herrera pushed:

- Fix object identities for pg_conversion objects.  This was already
  fixed in 0d906798f, but I failed to update the array-formatted case.
  This is not backpatched, since this only affects the code path
  introduced by commit a676201490c.
  http://git.postgresql.org/pg/commitdiff/70dc2db7f1dfdecdacf595bf00964cb20ad5a835

- pg_event_trigger_dropped_objects: add is_temp column.  It now also
  reports temporary objects dropped that are local to the backend.
  Previously we weren't reporting any temp objects because it was
  deemed unnecessary; but as it turns out, it is necessary if we want
  to keep close track of DDL command execution inside one session.
  Temp objects are reported as living in schema pg_temp, which works
  because such a schema-qualification always refers to the temp
  objects of the current session.
  http://git.postgresql.org/pg/commitdiff/e9a077cad3799b41e8deef6fd8cb87e50164a791

- Remove variable shadowing.  Commit a2e35b53 should have removed the
  variable declaration in the inner block, but didn't.  As a result,
  the returned address might end up not being what was intended.
  http://git.postgresql.org/pg/commitdiff/4e17e32f53c2de4a862ee5ef8bdcfa9152c11e25

- Fix autovacuum launcher shutdown sequence.  It was previously
  possible to have the launcher re-execute its main loop before
  shutting down if some other signal was received or an error occurred
  after getting SIGTERM, as reported by Qingqing Zhou.  While
  investigating, Tom Lane further noticed that if autovacuum had been
  disabled in the config file, it would misbehave by trying to start a
  new worker instead of bailing out immediately -- it would consider
  itself as invoked in emergency mode.  Fix both problems by checking
  the shutdown flag in a few more places.  These problems have existed
  since autovacuum was introduced, so backpatch all the way back.
  http://git.postgresql.org/pg/commitdiff/5df64f298d2863c9fb39437abb3ae6f988aedc0a

- Change SQLSTATE for event triggers "wrong context" message.  When
  certain event-trigger-only functions are called when not in the
  wrong context, they were reporting the "feature not supported"
  SQLSTATE, which is somewhat misleading.  Create a new custom error
  code for such uses instead.  Not backpatched since it may be seen as
  an undesirable behavioral change.  Author: Michael Paquier.
  Discussion:
  https://www.postgresql.org/message-id/CAB7nPqQ-5NAkHQHh_NOm7FPep37NCiLKwPoJ2Yxb8TDoGgbYYA <at> mail.gmail.com
  http://git.postgresql.org/pg/commitdiff/73206812cd97436cffd8f331dbb09d38a2728162

- Optimize locking a tuple already locked by another subxact.  Locking
  and updating the same tuple repeatedly led to some strange
  multixacts being created which had several subtransactions of the
  same parent transaction holding locks of the same strength.
  However, once a subxact of the current transaction holds a lock of a
  given strength, it's not necessary to acquire the same lock again.
  This made some coding patterns much slower than required.  The fix
  is twofold.  First we change HeapTupleSatisfiesUpdate to return
  HeapTupleBeingUpdated for the case where the current transaction is
  already a single-xid locker for the given tuple; it used to return
  HeapTupleMayBeUpdated for that case.  The new logic is simpler, and
  the change to pgrowlocks is a testament to that: previously we
  needed to check for the single-xid locker separately in a very ugly
  way.  That test is simpler now.  As fallout from the HTSU change,
  some of its callers need to be amended so that
  tuple-locked-by-own-transaction is taken into account in the
  BeingUpdated case rather than the MayBeUpdated case.  For many of
  them there is no difference; but heap_delete() and heap_update now
  check explicitely and do not grab tuple lock in that case.  The HTSU
  change also means that routine MultiXactHasRunningRemoteMembers
  introduced in commit 11ac4c73cb895 is no longer necessary and can be
  removed; the case that used to require it is now handled naturally
  as result of the changes to heap_delete and heap_update.  The second
  part of the fix to the performance issue is to adjust
  heap_lock_tuple to avoid the slowness: 1. Previously we checked for
  the case that our own transaction already held a strong enough lock
  and returned MayBeUpdated, but only in the multixact case.  Now we
  do it for the plain Xid case as well, which saves having to
  LockTuple.  2. If the current transaction is the only locker of the
  tuple (but with a lock not as strong as what we need; otherwise it
  would have been caught in the check mentioned above), we can skip
  sleeping on the multixact, and instead go straight to create an
  updated multixact with the additional lock strength.  3. Most
  importantly, make sure that both the single-xid-locker case and the
  multixact-locker case optimization are applied always.  We do this
  by checking both in a single place, rather than them appearing in
  two separate portions of the routine -- something that is made
  possible by the HeapTupleSatisfiesUpdate API change.  Previously we
  would only check for the single-xid case when HTSU returned
  MayBeUpdated, and only checked for the multixact case when HTSU
  returned BeingUpdated.  This was at odds with what HTSU actually
  returned in one case: if our own transaction was locker in a
  multixact, it returned MayBeUpdated, so the optimization never
  applied.  This is what led to the large multixacts in the first
  place.  Per bug report #8470 by Oskari Saarenmaa.
  http://git.postgresql.org/pg/commitdiff/27846f02c176eebe7e08ce51ed4d52140454e196

Simon Riggs pushed:

- Fix spelling of author's name
  http://git.postgresql.org/pg/commitdiff/1cdf4d0b6ac41e200d904d3fe293e43e07fd3e3c

Heikki Linnakangas pushed:

- Fix process startup in pg_rewind.  Don't allow pg_rewind to run as
  root on Unix platforms, as any new or replaced files in the data
  directory would become owned by root. On Windows, it can run under a
  user that has Administrator rights, but a restricted token needs to
  be used. This is the same we do e.g. in pg_resetxlog.  Also, add
  missing set_pglocale_pgservice() call, to fix localization.  Michael
  Paquier and Fujii Masao
  http://git.postgresql.org/pg/commitdiff/8a06c36aff4a94e5ffc3876cd85a1a16a82c754e

- Fix reporting of missing or invalid command line arguments in
  pg_rewind.  pg_fatal never returns, so a multi-line message cannot
  be printed by calling it twice.  Michael Paquier and Fujii Masao
  http://git.postgresql.org/pg/commitdiff/ee075fcb130f834bd5913940b97ad53fd4d21e93

- Gitignore temp files generated by SSL regression suite.  Michael
  Paquier
  http://git.postgresql.org/pg/commitdiff/0fb256dc8291657489e75ebb9cedc9a5012348ef

- Make SSL regression test suite more portable by avoiding cp.  Use
  perl 'glob' and File::Copy instead of "cp". This takes us one step
  closer to running the suite on Windows.  Michael Paquier
  http://git.postgresql.org/pg/commitdiff/5d79b67bdd57c2fed3e66f5102bd79e88ecb5af3

- Remove duplicated words in comments.  David Rowley
  http://git.postgresql.org/pg/commitdiff/a10589a5128e841d3faf94a2d8417a4f5497c4ac

- Free leaked result set in pg_rewind.  It was not significant in
  practice, it was just one instance of a small result set, but let's
  pacify Coverity.  Michael Paquier
  http://git.postgresql.org/pg/commitdiff/74a68e37d059295e97cc55683c9342912a0ec81f

Tom Lane pushed:

- Fix assorted inconsistent function declarations.  While gcc doesn't
  complain if you declare a function "static" and then define it
  not-static, other compilers do; and in any case the code is highly
  misleading this way.  Add the missing "static" keywords to a couple
  of recent patches.  Per buildfarm member pademelon.
  http://git.postgresql.org/pg/commitdiff/393de3a09868458dfb7ef765c544c34624ea1da2

Robert Haas pushed:

- Make trace_sort control abbreviation debug output for the text
  opclass.  This is consistent with what the new numeric suppor for
  abbreviated keys now does, and seems much more convenient than
  having a separate compiler define to control this debug output.
  Peter Geoghegan
  http://git.postgresql.org/pg/commitdiff/aea652abd3b6e41eeab58e14dfe3d3120592b443

Bruce Momjian pushed:

- libpq:  issue clear error message for nested service files.
  Previously an odd error message was generated.  Nested service files
  are not supported.  Report by David Johnston
  http://git.postgresql.org/pg/commitdiff/90a8b1f82b826ebe18a70e47dec3b342d7fcd8d9

- libpq:  add newlines to SSPI error messages.  Report by Tom Lane
  http://git.postgresql.org/pg/commitdiff/e4f1e0d842fa8e52d5972b19677ede5c36f44e98

Andres Freund pushed:

- Fix typo in eb68379c3.  I'd accidentally missed to rename
  PG_FORCE_NULL to BKI_FORCE_NULL in one place.  Author: Jeevan Chalke
  Discussion:
  CAM2+6=VPoow5PqgqiTjPX4QNeokb7op8aD_8Zg3QnHZMvvU0GQ <at> mail.gmail.com
  http://git.postgresql.org/pg/commitdiff/06d36fa40c5bf86004f9c968552f7cdb8f606d6d

Magnus Hagander pushed:

- Fix incorrect punctuation.  Amit Langote
  http://git.postgresql.org/pg/commitdiff/8ae4600cd9a079981168def863edb38ef237da6c

- Fix typo.  Michael Paquier
  http://git.postgresql.org/pg/commitdiff/c9970ab937d53a169e3e9e6522963db7a530b7ee

- Show owner of types in psql \dT+
  http://git.postgresql.org/pg/commitdiff/a6f3c1f1e2c365dd7dee1e944389d62bf62aa22e

- Add system view pg_stat_ssl.  This view shows information about all
  connections, such as if the connection is using SSL, which cipher is
  used, and which client certificate (if any) is used.  Reviews by
  Alex Shulgin, Heikki Linnakangas, Andres Freund & Michael Paquier
  http://git.postgresql.org/pg/commitdiff/9029f4b37406b21abb7516a2fd5643e0961810f8

Peter Eisentraut pushed:

- libpq: Don't overwrite existing OpenSSL thread callbacks.  If
  someone else already set the callbacks, don't overwrite them with
  ours.  When unsetting the callbacks, only unset them if they point
  to ours.  Author: Jan Urbański <wulczer <at> wulczer.org>
  http://git.postgresql.org/pg/commitdiff/8a0d34e4e45d44884ebdc6cb9d9ad9c3891d8505

- Move pg_archivecleanup from contrib/ to src/bin/.  Reviewed-by:
  Michael Paquier <michael.paquier <at> gmail.com>
  http://git.postgresql.org/pg/commitdiff/83aca89f7c3f913d960e2ea2d4d93b7d8e7a691d

== Rejected Patches (for now) ==

No one was disappointed this week :-)

== Pending Patches ==

Fabrízio de Royes Mello sent in two more revisions of a patch to
refactor reloptions to set locklevel.

Artem Luzyanin sent in two revisions of a patch to consolidate the
documentation of spinlocks and like kind items.

Emre Hasegeli sent in another revision of a patch to add a BRIN range
operator class.

Tomas Vondra sent in a patch to use foreign keys to improve join
estimates.

Michael Paquier sent in a patch to ignore some binaries generated in
src/test.

SAWADA Masahiko and Fabrízio de Royes Mello traded patches to add
REINDEX ... VERBOSE.

Shigeru HANADA sent in four more revisions of a patch to add a foreign
join API.

Petr Jelinek sent in another revision of a patch to implement
TABLESAMPLE.

Craig Ringer sent in a patch to add a pid column to
pg_replication_slots.

Peter Eisentraut and Pavel Stehule traded patches to add TRANSFORMS.

Michael Paquier sent in another revision of a patch to add an error
code to track unsupported contexts.

Álvaro Herrera sent in two more revisions of a patch to add deparsing
utilities.

Peter Geoghegan sent in another revision of a patch to implement
INSERT ... ON CONFLICT UPDATE (and IGNORE).

Tom Lane sent in another revision of a patch to implement UPDATE (*)
SET ...

Fujii Masao sent in another revision of a patch to remove the obsolete
FORCE option from REINDEX.

Dean Rasheed sent in another revision of a patch to fix some
infelicities in the error reporting for row-level access control.

Kyotaro HORIGUCHI sent in another revision of a patch to implement
regnamespace and regrole.

Antonin Houska sent in a patch to fix some issues in xlogreader.

Craig Ringer sent in two revisions of a patch to make pg_dump -t take
materialized views, matview data, foreign tables, and sequences.

Bruce Momjian sent in two revisions of a patch to ensure that CREATE
TABLE (LIKE...) preserves the relhasoids setting.

Michael Paquier sent in another revision of a patch to suppport TAP
tests with MSVC and Windows.

Jan Urbański sent in another revision of a patch to fix a bug in
libpq's multi-threaded SSL callback handling.

Ian Stakenvicius sent in a patch to fix an issue on Gentoo where
postgres fails to start with timezone-data >=2013e.

Etsuro Fujita sent in another revision of a patch to fix a problem
where EvalPlanQual behaves oddly for FDW queries involving system
columns.

Pavel Stehule sent in a patch to add a "raw" output option to COPY.

Chen Huajun sent in a patch to prevent setting Win32 server-side
socket buffer size on Windows 2012.

David Rowley sent in a patch to fix a few appendStringInfo* calls that
were not quite doing things the way as intended.

Michael Paquier sent in another revision of a patch to help improve
the performance of make check-world.

Heikki Linnakangas sent in a patch to remove xlogrecord padding.

--

-- 
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 | 13 Apr 10:07 2015

pgBdager release 6.4 is out

Paris, France - April 13th, 2015

DALIBO announce pgBadger 6.4, a maintenance release with some improvements.

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

This new release fixes a major bug in SQL beautifier which removed
operators.
It also adds some useful improvement in anonymization of parameters values.
pgBadger will now try to parse the full csvlog when a broken CSV line is
encountered instead of terminating the parsing.

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 Hubert
Depesz Lubaczewski, Sergey Burladyan and Thomas Reiss.

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

Marko Kreen | 9 Apr 17:38 2015
Picon

PgBouncer 1.5.5

This is a hotfix release with single fix only:

    * Fix remote crash - invalid packet order causes lookup of NULL
      pointer.  Not exploitable, just DoS.

PgFoundry is mostly dead, at the moment downloads are set up here:

  https://pgbouncer.github.io/downloads/

-- 
marko

--

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

Yugo Nagata | 8 Apr 10:34 2015
Picon

pgpool-II 3.4.2, 3.3.6, 3.2.11, 3.1.14, and 3.0.17 released

Pgpool Global Development Group is pleased to announce the availability
of pgpool-II 3.4.2, 3.3.6, 3.2.11, 3.1.14, and 3.0,18. These are the
latest  stable minor versions of each major versions of pgpool-II.

You can download them from:
http://pgpool.net/mediawiki/index.php/Downloads

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

                        3.4.2 (tataraboshi) 2015/04/08

* Version 3.4.2

    This is a bugfix release against pgpool-II 3.4.1.

    __________________________________________________________________

* Bug fixes

    - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
      (Nozomi Anzai)

    - Fix to reset on_exit call back functions in exec_if_cmd and exec_ping
      worker processes (Muhammad Usama)

      exec_if and exec_ping child processes were inheriting the parent exit
      callback functions which could result in undesired behavior if one of
      these commands fails. Fixed by adding on_exit_reset() at child start-up
      in both processes.

    - Fix to use void * type for receiving return value of thread function
      (Yugo Nagata)

      Previously int type was used and this could occur stack buffer
      overflow. This caused an infinity loop of ping error at bringing
      up or down VIP.

    - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog processes
      (Yugo Nagata)

      When using waitpid, it isn't necessary to set SIGCHLD to SIG_IGN.
      Rather, it is harmful, and due to this it was regarded that ping
      command exited abnormally in error even when this succeeded.

    - Fix to use waitpid instead of wait in exec_ifconifg (Yugo Nagata)

    - Remove an unnecessary include directive (Yugo Nagata)

    - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii)

      This is used in show pool_status command and limits the length of
      parameter description.  Unfortunately recovery_timeout description is
      64 chars, which is 1 byte longer than former definition of the macro.

    - doc: Update document of condition for load balancig (Yugo Nagata)

      Load balancing is possible in an explicit transaction block
      even in replication mode since 3.3.0.

    - Support SSL certificate chains in the certificate file for incoming
      frontend connections (Muhammad Usama)

    - Use to_regclass if available in time stamp rewriting in replication
      mode (Tatsuo Ishii)

    - Fix to not emits a fatal error message when clear text password auth
      is used (Muhammad Usama)

      The problem was introduced in pgpool-II after inclusion of exception
      manager. EOF on the frontend connection during client authentication
      should not be treated as an error when the password authentication
      method is used. psql disconnects from the server in such case to get
      the password from the terminal, reconnects and sends the read password
      to server.

    - previous session for the same child had exited because of some ERROR.
      (Muhammad Usama)

    - Fix a hang when an error occurs in a transaction block with
      replication mode (Yugo Nagata)

      When an error occurs at a backend node in a transaction block with
      replication mode, pgpool-II sends an invalid query to other
      backends to sync transaction states. However, previously, this was
      not sent to master node, and pgpool-II was waiting for master's
      response forever.

    - Fix a problem with pcp_detach_node about graceful node detach (Muhammad Usama)

      When graceful node detach is requested gracefully, pcp_detach_node should
      check if it is allowed to process detach_node command on the particular
      node before blocking the incoming connections and closing the existing
      connections.

    - doc: Update table and flowchart of where a query should be sent to
      (Yugo Nagata)

    - rpm: pgpool.spec is required only in RHEL/CentOS 7 (Nozomi Anzai)

    - Fix a compilation issue about sighandler_t type on BSD variants
      (Muhammad Usama)

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

                        3.3.6 (tokakiboshi) 2015/04/08

* Version 3.3.6

    This is a bugfix release against pgpool-II 3.3.5.

    __________________________________________________________________

* Bug fixes

    - rpm: Fix %tmpfiles_create to not be executed in RHEL/CentOS 6
      (Nozomi Anzai)

    - Fix to use void * type for receiving return value of thread function
      (Yugo Nagata)

      Previously int type was used and this could occur stack buffer
      overflow. This caused an infinity loop of ping error at bringing
      up or down VIP.

    - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog processes
      (Yugo Nagata)

      When using waitpid, it isn't necessary to set SIGCHLD to SIG_IGN.
      Rather, it is harmful, and due to this it was regarded that ping
      command exited abnormally in error even when this succeeded.

    - Remove an unnecessary include directive (Yugo Nagata)

    - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii)

      This is used in show pool_status command and limits the length of
      parameter description.  Unfortunately recovery_timeout description is
      64 chars, which is 1 byte longer than former definition of the macro.

    - doc: Update document of condition for load balancig (Yugo Nagata)

      Load balancing is possible in an explicit transaction block
      even in replication mode since 3.3.0.

    - Support SSL certificate chains in the certificate file for incoming
      frontend connections (Muhammad Usama)

    - Use to_regclass if available in time stamp rewriting in replication
      mode (Tatsuo Ishii)

    - Fix a hang when an error occurs in a transaction block with
      replication mode (Yugo Nagata)

      When an error occurs at a backend node in a transaction block with
      replication mode, pgpool-II sends an invalid query to other
      backends to sync transaction states. However, previously, this was
      not sent to master node, and pgpool-II was waiting for master's
      response forever.

    - Fix a problem with pcp_detach_node about graceful node detach (Muhammad Usama)

      When graceful node detach is requested gracefully, pcp_detach_node should
      check if it is allowed to process detach_node command on the particular
      node before blocking the incoming connections and closing the existing
      connections.

    - doc: Update table and flowchart of where a query should be sent to
      (Yugo Nagata)

    - rpm: pgpool.service is required only in RHEL/CentOS 7 (Nozomi Anzai)

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

                        3.2.11 (namameboshi) 2015/04/08

* Version 3.2.11

    This is a bugfix release against pgpool-II 3.2.10.

    __________________________________________________________________

* Bug fixes

    - Fix to use void * type for receiving return value of thread function
      (Yugo Nagata)

      Previously int type was used and this could occur stack buffer
      overflow. This caused an infinity loop of ping error at bringing
      up or down VIP.

    - Fix to set SIGCHLD to SIG_DFL instead of SIG_IGN in watchdog processes
      (Yugo Nagata)

      When using waitpid, it isn't necessary to set SIGCHLD to SIG_IGN.
      Rather, it is harmful, and due to this it was regarded that ping
      command exited abnormally in error even when this succeeded.

    - Remove an unnecessary include directive (Yugo Nagata)

    - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii)

      This is used in show pool_status command and limits the length of
      parameter description.  Unfortunately recovery_timeout description is
      64 chars, which is 1 byte longer than former definition of the macro.

    - Support SSL certificate chains in the certificate file for incoming
      frontend connections (Muhammad Usama)

    - Fix a problem with pcp_detach_node about graceful node detach (Muhammad Usama)

      When graceful node detach is requested gracefully, pcp_detach_node should
      check if it is allowed to process detach_node command on the particular
      node before blocking the incoming connections and closing the existing
      connections.

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

                        3.1.14 (hatsuiboshi) 2015/04/08

* Version 3.1.14

    This is a bugfix release against pgpool-II 3.1.13.

    __________________________________________________________________

* Bug fixes

    - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii)

      This is used in show pool_status command and limits the length of
      parameter description.  Unfortunately recovery_timeout description is
      64 chars, which is 1 byte longer than former definition of the macro.

    - Support SSL certificate chains in the certificate file for incoming
      frontend connections (Muhammad Usama)

    - Fix a problem with pcp_detach_node about graceful node detach (Muhammad Usama)

      When graceful node detach is requested gracefully, pcp_detach_node should
      check if it is allowed to process detach_node command on the particular
      node before blocking the incoming connections and closing the existing
      connections.

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

                        3.0.18 (umiyameboshi) 2015/04/08

* Version 3.0.18

    This is a bugfix release against pgpool-II 3.0.17.

    __________________________________________________________________

* Bug fixes

    - Enlarge POOLCONFIG_MAXDESCLEN to 80 (Tatsuo Ishii)

      This is used in show pool_status command and limits the length of
      parameter description.  Unfortunately recovery_timeout description is
      64 chars, which is 1 byte longer than former definition of the macro.

    - Support SSL certificate chains in the certificate file for incoming
      frontend connections (Muhammad Usama)

    - Fix a problem with pcp_detach_node about graceful node detach (Muhammad Usama)

      When graceful node detach is requested gracefully, pcp_detach_node should
      check if it is allowed to process detach_node command on the particular
      node before blocking the incoming connections and closing the existing
      connections.

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

-- 
Yugo Nagata <nagata <at> sraoss.co.jp>

--

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

Devrim Gündüz | 7 Apr 05:23 2015

PGDay.TR 2015 Istanbul -- last week for CfP


Are you living at/close to Turkey? Here is a good chance to visit
Istanbul and meet with more PostgreSQL people!

Turkish PostgreSQL Users and Developers Association is organizing the
4th Turkish PostgreSQL Conference on 9 May 2015.

Following the 3rd conference held with the attendance of 250
participants, 17 speakers, 9 sponsors at TOBB University, this year more
than 300 participants are being expected for PgDay 2015 to take place
with the contributions of Boğaziçi University.

Dave Page, a core team member, will give the keynote.

This year, there will be a full English track, along with the Turkish
track(s), so we are expecting non-Turkish attendees from countries
nearby!

Conference is free and open to everyone.

Call for Papers: http://pgday.postgresql.org.tr/en/index.html#cfp

Registration:
http://pgday.postgresql.org.tr/en/index.html#register-section

Sponsorship:
http://pgday.postgresql.org.tr/en/index.html#sponsors

Regards,
--

-- 
Devrim GÜNDÜZ
Principal Systems Engineer  <at>  EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter:  <at> DevrimGunduz ,  <at> DevrimGunduzTR


Gmane