Postgres Plus Advanced Server v9.1 is now generally available

Postgres Plus Advanced Server v9.1.2 is now Generally Available.
Highlights of the release include: merge with the latest available
release of community PostgreSQL (v9.1.2 with synchronous replication
and fast in-memory tables0; Read Scalability Improvements on high CPU
count machines; Write Scalability improvements on high core count
machines; and 8th generation Oracle compatibility features including
Virtual Private Database, Partitioning syntax support and Ordered Hint
support.  Advanced Server is available now on Linux 32 and 64 bit
platforms, Windows 32 and 64 bit platforms, HP-UX and Solaris.

Downloads and Release Notes are available at
http://www.enterprisedb.com/download-advanced-server

The EnterpriseDB Team

Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

               pgsql-announce-unsubscribe <at> postgresql.org

pgreplay log file replayer 1.1.0 released

I announce the version 1.1.0 of pgreplay.

Project home page: http://pgreplay.projects.postgresql.org/

pgreplay reads a PostgreSQL log file (*not* a WAL file),
extracts the SQL statements and executes them in the same order
and relative time against a PostgreSQL database cluster.

If the execution of statements gets behind schedule, warning
messages are issued that indicate that the server cannot handle
the load in a timely fashion.
The idea is to replay a real-world database workload as exactly
as possible.

pgreplay is useful for performance tests, particularly in the
following situations:

* You want to compare the performance of your PostgreSQL
  application on different hardware or different operating systems.
* You want to upgrade your database and want to make sure that
  the new database version does not suffer from performance
  regressions that affect you.

Features:
 * Should compile and run on any platform that PostgreSQL supports
 * Can replay the workload at different speeds
 * Can parse "stderr" and "csvlog" log files
 * Can save workload to replay in "replay file" for reuse
 * Outputs detailed parse and execution statistics

Scalr 2.5 supports PostgreSQL

== PostgreSQL Weekly News - February 05 2012 ==

== PostgreSQL Weekly News - February 05 2012 ==

PGDay France will be in Lyon on June 7, 2012.
http://www.pgday.fr

PGDay NYC will be held April 2, 2012 at Lighthouse International in
New York City.
http://pgday.nycpug.org

== PostgreSQL Product News ==

MyJSQLView Version 3.31 Released.
http://dandymadeproductions.com/projects/MyJSQLView/

Slony-I 2.1.1 & 1.2.23 released.
http://www.slony.info/

== PostgreSQL Jobs for February ==

http://archives.postgresql.org/pgsql-jobs/2012-02/threads.php

== PostgreSQL Local ==

The fifth annual "Prague PostgreSQL Developers Day" conference,
organized by CSPUG (Czech and Slovak PostgreSQL Users Group), will be
held on February 9, 2012 in Prague.

PGDay NYC will be held April 2, 2012 at Lighthouse International in
New York City.
http://pgday.nycpug.org

PGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of
Ottawa.  It will be preceded by two days of tutorials on 15-16 May 2012.
http://www.pgcon.org/2012/

PGDay France will be in Lyon on June 7, 2012.
http://www.pgday.fr

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

== Reviews ==

== Applied Patches ==

Heikki Linnakangas pushed:

- Accept a non-existent value in "ALTER USER/DATABASE SET ..."
  command.  When default_text_search_config, default_tablespace, or
  temp_tablespaces setting is set per-user or per-database, with an
  "ALTER USER/DATABASE SET ..." statement, don't throw an error if the
  text search configuration or tablespace does not exist. In case of
  text search configuration, even if it doesn't exist in the current
  database, it might exist in another database, where the setting is
  intended to have its effect. This behavior is now the same as
  search_path's.  Tablespaces are cluster-wide, so the same argument
  doesn't hold for tablespaces, but there's a problem with pg_dumpall:
  it dumps "ALTER USER SET ..." statements before the "CREATE
  TABLESPACE" statements.  Arguably that's pg_dumpall's fault - it
  should dump the statements in such an order that the tablespace is
  created first and then the "ALTER USER SET default_tablespace ..."
  statements after that - but it seems better to be consistent with
  search_path and default_text_search_config anyway.  Besides, you
  could still create a dump that throws an error, by creating the
  tablespace, running "ALTER USER SET default_tablespace", then
  dropping the tablespace and running pg_dumpall on that.  Backpatch
  to all supported versions.
  http://git.postgresql.org/pg/commitdiff/a5782570402988205b3a42ed40f7bc157eac21fc

- Make group commit more effective.  When a backend needs to flush the
  WAL, and someone else is already flushing the WAL, wait until it
  releases the WALInsertLock and check if we still need to do the
  flush or if the other backend already did the work for us, before
  acquiring WALInsertLock. This helps group commit, because when the
  WAL flush finishes, all the backends that were waiting for it can be
  woken up in one go, and the can all concurrently observe that
  they're done, rather than waking them up one by one in a cascading
  fashion.  This is based on a new LWLock function,
  LWLockWaitUntilFree(), which has peculiar semantics. If the lock is
  immediately free, it grabs the lock and returns true. If it's not
  free, it waits until it is released, but then returns false without
  grabbing the lock. This is used in XLogFlush(), so that when the
  lock is acquired, the backend flushes the WAL, but if it's not, the
  backend first checks the current flush location before retrying.
  Original patch and benchmarking by Peter Geoghegan and Simon Riggs,
  although this patch as committed ended up being very different from
  that.
  http://git.postgresql.org/pg/commitdiff/9b38d46d9f5517dab67dda1dd0459683fc9cda9f

- Fix bug in the new wait-until-lwlock-is-free mechanism.  If there
  was a wait-until-free process in the head of the wait queue,
  followed by an exclusive locker, the exclusive locker was not be
  woken up as it should.
  http://git.postgresql.org/pg/commitdiff/82d4b262d9614958da38003cdc9d56915d9bcda0

- Print function signature, not just name, in PL/pgSQL error messages.
  This makes it unambiguous which function the message is coming from,
  if you have overloaded functions.  Pavel Stehule, reviewed by
  Abhijit Menon-Sen.
  http://git.postgresql.org/pg/commitdiff/4c6cedd1b014abf2046886a9a92e10e18f0d658e

Simon Riggs pushed:

- Various minor comments changes from bgwriter to checkpointer.
  http://git.postgresql.org/pg/commitdiff/73f617f13f4ca185977d9f7b09bf9edc491cd12f

- Minor bug fix and cleanup from self-review of sync rep queues patch.
  http://git.postgresql.org/pg/commitdiff/ba1868ba3138b2119f8290969b9a3936fbc297ce

Robert Haas pushed:

- Remove prototype for nonexistent function.
  http://git.postgresql.org/pg/commitdiff/423ee49b491ee966aa06259772dc38819cab786a

- Built-in JSON data type.  Like the XML data type, we simply store
  JSON data as text, after checking that it is valid.  More complex
  operations such as canonicalization and comparison may come later,
  but this is enough for not.  There are a few open issues here, such
  as whether we should attempt to detect UTF-8 surrogate pairs
  represented as \uXXXX\uYYYY, but this gets the basic framework in
  place.
  http://git.postgresql.org/pg/commitdiff/5384a73f98d9829725186a7b65bf4f8adb3cfaf1

- Catversion bump for JSON patch.  Sigh.
  http://git.postgresql.org/pg/commitdiff/c327108140b5dfc4db1fcb9d9ca647f483e0a153

- Adjust expected regression test outputs for PL/python.  This got
  broken by commit 4c6cedd1b014abf2046886a9a92e10e18f0d658e, which
  caused PL/pgsql error messages to print the function signature, not
  just the name.  Per buildfarm.
  http://git.postgresql.org/pg/commitdiff/5ae88c65da7d893e304a51bfc57b46d8b7653bd0

- Avoid re-checking for visibility map extension too frequently.  When
  testing bits (but not when setting or clearing them), we now won't
  check whether the map has been extended.  This significantly
  improves performance in the case where the visibility map doesn't
  exist yet, by avoiding an extra system call per tuple.  To make sure
  backends notice eventually, send an smgr inval on VM extension.
  Dean Rasheed, with minor modifications by me.
  http://git.postgresql.org/pg/commitdiff/b4e0741727685443657b55932da0c06f028fbc00

- Allow spgist's text_ops to handle pattern-matching operators.  This
  was presumably intended to work this way all along, but a few key
  bits of indxpath.c didn't get the memo.  Robert Haas and Tom Lane
  http://git.postgresql.org/pg/commitdiff/0ed7445d7317318ffed0d8dac9a06611771d315b

Peter Eisentraut pushed:

- Add sequence USAGE privileges to information schema.  The sequence
  USAGE privilege is sufficiently similar to the SQL standard that it
  seems reasonable to show in the information schema.  Also add some
  compatibility notes about it on the GRANT reference page.
  http://git.postgresql.org/pg/commitdiff/82e83f46a2ed311c6e7536f607f73a6f2a1d7dea

- Use abort() instead of exit() to abort library functions.  In some
  hopeless situations, certain library functions in libpq and
  libpgport quit the program.  Use abort() for that instead of exit(),
  so we don't interfere with the normal exit codes the program might
  use, we clearly signal the abnormal termination, and the caller has
  a chance of catching the termination.  This was originally pointed
  out by Debian's Lintian program.
  http://git.postgresql.org/pg/commitdiff/c6ea8ccea6bf23501962ddc7ac9ffdb99c8643e1

- PL/Python: Add result metadata functions.  Add result object
  functions .colnames, .coltypes, .coltypmods to obtain information
  about the result column names and types, which was previously not
  possible in the PL/Python SPI interface.  reviewed by Abhijit
  Menon-Sen
  http://git.postgresql.org/pg/commitdiff/ee7fa66b19f5454fac07caee4b7798810b579a82

- pg_dump: Add GCC noreturn attribute to appropriate functions.  This
  is a small help to the compiler and static analyzers.
  http://git.postgresql.org/pg/commitdiff/88a6ac9f93b138d39d08b9882b377539edf985f4

- psql: Reduce the amount of const lies a bit.
  http://git.postgresql.org/pg/commitdiff/4b77bfc37a1819fdfd3b767a52ff633cd28f9155

- psql: Case preserving completion of SQL key words.  Instead of
  always completing SQL key words in upper case, look at the word
  being completed and match the case.  reviewed by Fujii Masao
  http://git.postgresql.org/pg/commitdiff/69f4f1c3576abc535871c6cfa95539e32a36120f

- initdb: Add options --auth-local and --auth-host.  Reviewed by
  Robert Haas and Pavel Stehule
  http://git.postgresql.org/pg/commitdiff/8a02339e9ba3f2f962c5967be8c5d053a1fa39d2

- ecpg: Improve test building Further improve on commit
  c75e1436467f32a06b5ab9d594d2a390e7f4594d.  Instead of building both
  .o files and binaries in the same make rule, just rely on the normal
  .c -> .o rule.  This will ensure that dependency tracking is used
  when enabled.  To do this, disable the implicit direct .c -> binary
  rule globally, which will also prevent the original problem (*.dSYM
  junk) from reappearing elsewhere.

Tom Lane pushed:

- Code review for plpgsql fn_signature patch.  Don't quote the output
  of format_procedure(); it's already quoted quite enough.  Remove the
  fn_name field, which was now just dead weight.  Fix remaining
  expected-output files.
  http://git.postgresql.org/pg/commitdiff/bef47331b6a1c0d081179a7fc9b82dd7e1862394

- Try to be more consistent about accepting denormalized float8
  numbers.  On some platforms, strtod() reports ERANGE for a
  denormalized value (ie, one that can be represented as distinct from
  zero, but is too small to have full precision).  On others, it
  doesn't.  It seems better to try to accept these values
  consistently, so add a test to see if the result value indicates a
  true out-of-range condition.  This should be okay per Single Unix
  Spec.  On machines where the underlying math isn't IEEE standard,
  the behavior for such small numbers may not be very consistent, but
  then it wouldn't be anyway.  Marti Raudsepp, after a proposal by
  Jeroen Vermeulen
  http://git.postgresql.org/pg/commitdiff/c318aeed84438619fc6b8c647def1730a110f04b

- Add some regression test cases for denormalized float8 input.  This
  was submitted with the previous patch, but I'm committing it
  separately to ease backing it out if these results prove too
  unportable.  Marti Raudsepp, after a proposal by Jeroen Vermeulen
  http://git.postgresql.org/pg/commitdiff/500cf66d5522b39ddfdc26b309f8b5b0e385f42e

- Revert "Add some regression test cases for denormalized float8
  input." This reverts commit
  500cf66d5522b39ddfdc26b309f8b5b0e385f42e.  As was more or less
  expected, a small minority of platforms won't accept denormalized
  input even with the recent changes.  It doesn't seem especially
  helpful to test this if we're going to have to provide an alternate
  expected-file to allow failure.
  http://git.postgresql.org/pg/commitdiff/342b83fdca6af04d86e761f4d8d79e5d598688cd

- Allow SQL-language functions to reference parameters by name.
  Matthew Draper, reviewed by Hitoshi Harada
  http://git.postgresql.org/pg/commitdiff/9bff0780cf5be2193a5bad0d3df2dbe143085264

- Improve comment.
  http://git.postgresql.org/pg/commitdiff/ee68a44106fa89b8efb2f21b71c3fcafaaf48851

- Add missing Assert and fix inaccurate elog message in
  standby_redo().  All other WAL redo routines either call
  RestoreBkpBlocks() or Assert that they haven't been passed any
  backup blocks.  Make this one do likewise.  Also, fix incorrect
  routine name in its failure message.
  http://git.postgresql.org/pg/commitdiff/2af72cefeaa15e27277d327783fdec2748d9b758

- Fix transient clobbering of shared buffers during WAL replay.
  RestoreBkpBlocks was in the habit of zeroing and refilling the
  target buffer; which was perfectly safe when the code was written,
  but is unsafe during Hot Standby operation.  The reason is that we
  have coding rules that allow backends to continue accessing a tuple
  in a heap relation while holding only a pin on its buffer.  Such a
  backend could see transiently zeroed data, if WAL replay had
  occasion to change other data on the page.  This has been shown to
  be the cause of bug #6425 from Duncan Rance (who deserves kudos for
  developing a sufficiently-reproducible test case) as well as Bridget
  Frey's re-report of bug #6200.  It most likely explains the original
  report as well, though we don't yet have confirmation of that.  To
  fix, change the code so that only bytes that are supposed to change
  will change, even transiently.  This actually saves cycles in
  RestoreBkpBlocks, since it's not writing the same bytes twice.  Also
  fix seq_redo, which has the same disease, though it has to work a
  bit harder to meet the requirement.  So far as I can tell, no other
  WAL replay routines have this type of bug.  In particular, the
  index-related replay routines, which would certainly be broken if
  they had to meet the same standard, are not at risk because we do
  not have coding rules that allow access to an index page when not
  holding a buffer lock on it.  Back-patch to 9.0 where Hot Standby
  was added.
  http://git.postgresql.org/pg/commitdiff/17118825b8164aac6d337b58cf66b17637c66a49

Alvaro Herrera pushed:

- Properly free the sslcompression field in PGconn.  Marko Kreen
  http://git.postgresql.org/pg/commitdiff/21238deea50e194bfa1c844b01ffbd15ed56c01a

- Implement dry-run mode for pg_archivecleanup.  In dry-run mode, just
  the name of the file to be removed is printed to stdout; this is so
  the user can easily plug it into another program through a pipe.  If
  debug mode is also specified, a more verbose message is printed to
  stderr.  Author: Gabriele Bartolini Reviewer: Josh Kupershmidt
  http://git.postgresql.org/pg/commitdiff/b2e431a4db81a735d1474c4d1565a20b835878c9

Andrew Dunstan pushed:

- Add array_to_json and row_to_json functions.  Also move the
  escape_json function from explain.c to json.c where it seems to
  belong.  Andrew Dunstan, Reviewd by Abhijit Menon-Sen.
  http://git.postgresql.org/pg/commitdiff/39909d1d39ae57c3a655fc7010e394e26b90fec9

Michael Meskes pushed:

- Applied Peter's patch to PQconnectdbParams in ecpglib instead of the
  old PQconectdb.
  http://git.postgresql.org/pg/commitdiff/fc211f8277c06326fcd5012f7247528920376a4c

Bruce Momjian pushed:

- Remove tabs in SGML file.
  http://git.postgresql.org/pg/commitdiff/072ba77bffe005ccd6d1aaf8fff2c52ebed1a8b3

== Rejected Patches (for now) ==

No one was disappointed this week 

== Pending Patches ==

Alexander Korotkov sent in another revision of the patch to add GiST
indexing for range types, per review by Jeff Davis.

Kyotaro HORIGUCHI and Marko Kreen traded patches to speed dblink by
creating and using a new libpq tuple storage method.

Gilles Darold sent in a patch to implement pg_is_in_backup().

Alvaro Herrera sent in another revision of the FOREIGN KEY locks
patch.

Robert Haas and Simon Riggs traded patches to implement DROP INDEX
CONCURRENTLY.

Andrew Dunstan sent in a patch to fix an issue where pg_dump -s could
dump data if it came from an extension.

Shigeru HANADA sent in another revision of the patch to implement a
PostgreSQL FDW.

Heikki Linnakangas sent in another revision of the patch to scale xlog
insertion.

Peter Eisentraut sent in another revision of the patch to enable
renaming constraints in an ALTER TABLE statement.

Chetan Suttraway sent in a patch to implement SPI_gettypemod().

Simon Riggs sent in a patch refactoring log_newpage.

Alvaro Herrera sent in a patch to fix an issue where heap_tuple_read
could get a false positive.

Alvaro Herrera sent in a patch to make options in pg_hba.conf be
case-insensitive.

Oleg Bartunov sent in a patch to support NULLs in SP-GiST.

Robert Haas sent in another revision of the patch to allow EXPLAIN
ANALYZE not to include timing information.

Marti Raudsepp sent in another revision of the patch to cache stable
expressions with constant arguments.

KaiGai Kohei sent in another revision of the patch to unify the
permissions checks on DROP.

KaiGai Kohei sent in another revision of the patch to add a
sepgsql.client_label GUC.

Thomas Munro sent in a patch to add an optional SKIP LOCKED DATA to
SELECT ... FOR (UPDATE | SHARE ).

Jeff Janes sent in another revision of the patch to use less memory
during sorting.

Jeff Davis sent in a patch to fix an issue where it was possible for
things to happen between an initdb call and its actually getting
written out to disk.

Simon Riggs sent in another revision of the patch to fix an issue in
slot_deform_tuple.

Jan Urbanski sent in a patch to fix a memory leak in PL/PythonU's
datum->dict transformation.

Jan Urbanski sent in a patch to fix a memory leak in PL/PythonU's
datum->string transformation.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

               pgsql-announce-unsubscribe <at> postgresql.org

MyJSQLView Version 3.31 Released

The MyJSQLView project is pleased to release v3.33 to the public. The
release includes improvements in the efficiency of use for the SQL Query
Bucket and an Aggregation/GROUP BY feature for the Advanced Sort/Search
Form. The new release also brings a new default plugin called HeatMapper
that allows the plotting of multi-variable numeric data. Initial tests
for the HeatMapper plugin used latitude, longitude, and temperature
data from measurements in the Alantic with over 90k records. The coding
for this plugin solidified the selection of HyperSQL for in memory data
analysis.

Dana M. Proctor
MyJSQLView Project Manager
http://dandymadeproductions.com/projects/MyJSQLView/

MyJSQLView provides an easy to use free Open Source Java based user
interface frontend for viewing, adding, editing, or deleting entries
in several mainstream databases including PostgreSQL. A query frame
allows the building of complex SQL statements. The application allows
easy sorting, searching, and import/export of table data.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

               pgsql-announce-unsubscribe <at> postgresql.org

Slony-I 2.1.1 & 1.2.23 released

The Slony-I team is pleased to announce the release of Slony-I 2.1.1
a bug fix release for the 2.1 stream. and Slony-I 1.2.23 a bug fix 
release in the 1.2 stream.

2.1.1
=============

- Bug #260 :: Fixed issue when with FAILOVER command when the failed 
node has multiple sets.

- Bug #246 :: Include path order changes
- Bug #161 :: fix memory overrun in EXECUTE SCRIPT parser
- Bug #247 :: slony_logshipper to handle TRUNCATE commands
- Bug #249 :: Add parentheses to txid_current() in function for
               TRUNCATE logging
- slonik_drop_table and slonik_drop_sequence no longer attempt to
   return -1 on an error (invalid as a slonik exit code in 2.1)
- Bug #244 :: The CREATE SET command now requires a set id to be specified.
- Bug #255 :: Fix serialization conflict issues when using PostgreSQL 9.1.
- Bug #256 :: set_conf_option() has an extra elevel parameter on PG 9.2
- Bug #259 :: Fix TRUNCATE logging so it works with mixed case slony 
clusters.

http://www.slony.info/downloads/2.1/source/slony1-2.1.1.tar.bz2
http://www.slony.info/downloads/2.1/source/slony1-2.1.1-docs.tar.bz2

1.2.23
===========
- Bug #195 - make slon_quote_* functions immutable
- Bug #209 - dollar quoting doesn't work on PG 7.4
- Bug #224 - PKEYEDTABLES misspelled in altperl script
- Bug #236 - fix misformatting of log string for timestamp
- Bug #239 - Fix FAILOVER on PG 9.0 by not querying pg_listener

http://www.slony.info/downloads/1.2/source/slony1-1.2.23.tar.bz2
http://www.slony.info/downloads/1.2/source/slony1-1.2.23-docs.tar.bz2

Unless additional maintainers from the community step up 1.2.23 is 
likely to be the last 1.2.x release.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

               pgsql-announce-unsubscribe <at> postgresql.org

== PostgreSQL Weekly News - January 29 2012 ==

== PostgreSQL Weekly News - January 29 2012 ==

There will be a PostgreSQL track at FOSDEM, February 4-5 in Brussels,
Belgium, along with speakers from the PostgreSQL community on the main
track.
http://fosdem.org/2012/

The PGCon CfP has been extended through January 31, 2012.
http://www.pgcon.org/2012/papers.php

PGDay NYC will be held April 2, 2012 at Lighthouse International in
New York City.
http://pgday.nycpug.org

PGDay France will be in Lyon on June 7, 2012.
http://www.pgday.fr

== PostgreSQL Jobs for January ==

http://archives.postgresql.org/pgsql-jobs/2012-01/threads.php

== PostgreSQL Local ==

The fifth annual "Prague PostgreSQL Developers Day" conference,
organized by CSPUG (Czech and Slovak PostgreSQL Users Group), will be
held on February 9, 2012 in Prague.

PGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of
Ottawa.  It will be preceded by two days of tutorials on 15-16 May 2012.
http://www.pgcon.org/2012/

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

== Reviews ==

== Applied Patches ==

Simon Riggs pushed:

- ALTER <thing> [IF EXISTS] ... allows silent DDL if required, e.g.
  ALTER FOREIGN TABLE IF EXISTS foo RENAME TO bar.  Pavel Stehule
  http://git.postgresql.org/pg/commitdiff/b8a91d9d1c7ec75aaecf13df687ec7b5b0ed35a6

- Resolve timing issue with logging locks for Hot Standby.  We log
  AccessExclusiveLocks for replay onto standby nodes, but because of
  timing issues on ProcArray it is possible to log a lock that is
  still held by a just committed transaction that is very soon to be
  removed. To avoid any timing issue we avoid applying locks made by
  transactions with InvalidXid.  Simon Riggs, bug report Tom Lane,
  diagnosis Pavan Deolasee
  http://git.postgresql.org/pg/commitdiff/c172b7b02e6f6008d6dad66ddee8f67faf223c5b

- Add new replication mode synchronous_commit = 'write'.  Replication
  occurs only to memory on standby, not to disk, so provides
  additional performance if user wishes to reduce durability level
  slightly. Adds concept of multiple independent sync rep queues.
  Fujii Masao and Simon Riggs
  http://git.postgresql.org/pg/commitdiff/443b4821f1649bc617c5ce1f6f3ffc65842a8930

- Allow pg_basebackup from standby node with safety checking.  Base
  backup follows recommended procedure, plus goes to great lengths to
  ensure that partial page writes are avoided.  Jun Ishizuka and Fujii
  Masao, with minor modifications
  http://git.postgresql.org/pg/commitdiff/8366c7803ec3d0591cf2d1226fea1fee947d56c3

Robert Haas pushed:

- Adjustments to regression tests for security_barrier views.  Drop
  the role we create, so regression tests pass even when run more than
  once against the same cluster, a problem noted by Tom Lane and Jeff
  Janes.  Also, rename the temporary role so that it starts with
  "regress_", to make it unlikely that we'll collide with an existing
  role name while running "make installcheck", per further gripe from
  Tom Lane.
  http://git.postgresql.org/pg/commitdiff/49562f5eb66f31940dd7b64555bbd81bae952387

- Make CheckIndexCompatible simpler and more bullet-proof.  This gives
  up the "don't rewrite the index" behavior in a couple of relatively
  unimportant cases, such as changing between an array type and an
  unconstrained domain over that array type, in return for making this
  code more future-proof.  Noah Misch
  http://git.postgresql.org/pg/commitdiff/6eb71ac5527a94be443bc66e68b47b04979906e4

- Instrument index-only scans to count heap fetches performed.  Patch
  by me; review by Tom Lane, Jeff Davis, and Peter Geoghegan.
  http://git.postgresql.org/pg/commitdiff/9f9135d129e915e72c8a2f770689fd72619ead49

- Damage control for yesterday's CheckIndexCompatible changes.  Rip
  out a regression test that doesn't play well with settings put in
  place by the build farm, and rewrite the code in
  CheckIndexCompatible in a hopefully more transparent style.
  http://git.postgresql.org/pg/commitdiff/9d35116611e6a1fc10f2298944fbf0e4e1a826be

- Classify DROP operations by whether or not they are user-initiated.
  This doesn't do anything useful just yet, but is intended as
  supporting infrastructure for allowing sepgsql to sensibly check
  DROP permissions.  KaiGai Kohei and Robert Haas
  http://git.postgresql.org/pg/commitdiff/0e549697d1c6b8eeb623c497dc38a5aed4deea1e

- Add missing #include, to suppress compiler warning.
  http://git.postgresql.org/pg/commitdiff/467ff207f51439cadee7857d6a0874f34652ed53

- Be more clear when a new column name collides with a system column
  name.  We now use the same error message for ALTER TABLE .. ADD
  COLUMN or ALTER TABLE .. RENAME COLUMN that we do for CREATE TABLE.
  The old message was accurate, but might be confusing to users not
  aware of our system columns.  Vik Reykja, with some changes by me,
  and further proofreading by Tom Lane
  http://git.postgresql.org/pg/commitdiff/2d1371d3ee5cf7e96d16fb503c27e060df9497f7

- Adjust tuplesort.c based on the fact that we never use the OS's
  qsort().  Our own qsort_arg() implementation doesn't have the defect
  previously observed to affect only QNX 4, so it seems sufficiently
  to assert that it isn't broken rather than retesting.  Also, update
  a few comments to clarify why it's valuable to retain a tie-break
  rule based on CTID during index builds.  Peter Geoghegan, with
  slight tweaks by me.
  http://git.postgresql.org/pg/commitdiff/c5a03256c725c09c32a5c498bd7c8799ed3ec2a0

- pg_dump: Move connection-setup code to a separate function.
  Parallel dump will need to repeat these steps for each new
  connection, so it's better to have this logic in its own function.
  Extracted (with some changes) from a much larger patch by Joachim
  Wieland.
  http://git.postgresql.org/pg/commitdiff/e43166a557d5f28aa66fa15be12fdc6a8ebe380a

- Document that analyzing an empty table doesn't update the
  statistics.  Per a suggestion from Sergey Konoplev
  http://git.postgresql.org/pg/commitdiff/db6de5b71ef2d91dde94fc0de8adf45372bc332d

- Document that COUNT(*) might not need a seq scan any more.  Noted by
  Josh Kupershmidt.
  http://git.postgresql.org/pg/commitdiff/eb6af016fc04392c41106ac866072914bf66ecd0

Bruce Momjian pushed:

- Reduce tab outdent of "error handling" GUC comments in
  postgresql.conf, to match surrounding outdenting.
  http://git.postgresql.org/pg/commitdiff/890a9992ce78b691e44359236d8b47e3c889581d

- Fix new SQL tablespace location function usage in pg_upgrade to
  properly check cluster version numbers, and fix missing table alias.
  http://git.postgresql.org/pg/commitdiff/b95aec529014355f4f90c5095993404ff0291b02

- In pg_upgrade, when checking for the plpython library, we must check
  for "plpython2" when upgrading from pre-PG 9.1.  Patch to head and
  9.1.  Per report from Peter Eisentraut.
  http://git.postgresql.org/pg/commitdiff/cfe443ab9d42b4ffe950608f01c3a4bdc2895c7b

- Improve plpython fix comment in pg_upgrade.
  http://git.postgresql.org/pg/commitdiff/a7f2c79a6eebccd94aade2b03d40a2caeba8a5c3

- Now that the shared library name can be adjusted in the library
  test, have pg_upgrade allocate a maximum fixed size buffer for
  testing the library file name, rather than base the allocation on
  the library name.  Backpatch to 9.1.
  http://git.postgresql.org/pg/commitdiff/6d5aae7afacc564ead2af88c76b13cfc55750556

- Fix pg_upgrade --help text for --user to not use a plural cluster name.
  http://git.postgresql.org/pg/commitdiff/3946c281613e549d5686ad3f5b298549b0eb0efe

Tom Lane pushed:

- Suppress possibly-uninitialized-variable warning seen with older gcc
  versions.
  http://git.postgresql.org/pg/commitdiff/beef89567e3a0e3e1c753754a474065c5ad632fe

- Suppress variable-clobbered-by-longjmp warning seen with older gcc
  versions.
  http://git.postgresql.org/pg/commitdiff/f26c9896b3da1b6aa5c560c4743f22a2a6c84919

- Use parameterized paths to generate inner indexscans more flexibly.
  This patch fixes the planner so that it can generate nestloop-with-
  inner-indexscan plans even with one or more levels of joining
  between the indexscan and the nestloop join that is supplying the
  parameter.  The executor was fixed to handle such cases some time
  ago, but the planner was not ready.  This should improve our plans
  in many situations where join ordering restrictions formerly forced
  complete table scans.  There is probably a fair amount of tuning
  work yet to be done, because of various heuristics that have been
  added to limit the number of parameterized paths considered.
  However, we are not going to find out what needs to be adjusted
  until the code gets some real-world use, so it's time to get it in
  there where it can be tested easily.  Note API change for index AM
  amcostestimate functions.  I'm not aware of any non-core index AMs,
  but if there are any, they will need minor adjustments.
  http://git.postgresql.org/pg/commitdiff/e2fa76d80ba571d4de8992de6386536867250474

- Undo 8.4-era lobotomization of subquery pullup rules.  After the
  planner was fixed to convert some IN/EXISTS subqueries into
  semijoins or antijoins, we had to prevent it from doing that in some
  cases where the plans risked getting much worse.  The reason the
  plans got worse was that in the unoptimized implementation,
  subqueries could reference parameters from the outer query at any
  join level, and so full table scans could be avoided even if they
  were one or more levels of join below where the semi/anti join would
  be.  Now that we have sufficient mechanism in the planner to handle
  such cases properly, it should no longer be necessary to play dumb
  here.  This reverts commits 07b9936a0f10d746e5076239813a5e938f2f16be
  and cd1f0d04bf06938c0ee5728fc8424d62bcf2eef3.  The latter was a
  stopgap fix that wasn't really sufficiently analyzed at the time.
  Rather than just restricting ourselves to cases where the new join
  can be stacked on the right-hand input, we should also consider
  whether it can be stacked on the left-hand input.
  http://git.postgresql.org/pg/commitdiff/0816fad6eebddb8f1f0e21635e46625815d690b9

- Fix error detection in contrib/pgcrypto's encrypt_iv() and
  decrypt_iv().  Due to oversights, the encrypt_iv() and decrypt_iv()
  functions failed to report certain types of invalid-input errors,
  and would instead return random garbage values.  Marko Kreen, per
  report from Stefan Kaltenbrunner
  http://git.postgresql.org/pg/commitdiff/a8b4b84360e5ea145d12d372305b50f6774b0366

- Fix handling of data-modifying CTE subplans in EvalPlanQual.  We
  can't just skip initializing such subplans, because the referencing
  CTE node will expect to find the subplan available when it
  initializes.  That in turn means that ExecInitModifyTable must allow
  the case (which actually it needed to do anyway, since there's no
  guarantee that ModifyTable is exactly at the top of the CTE plan
  tree).  So move the complaint about not being allowed in
  EvalPlanQual mode to execution instead of initialization.  Testing
  turned up yet another problem, which is that we'd try to
  re-initialize the result relation's index list, leading to leaks and
  dangling pointers.  Per report from Phil Sorber.  Back-patch to 9.1
  where data-modifying CTEs were introduced.
  http://git.postgresql.org/pg/commitdiff/7c1719bc68ec1c347e7c80c3735bf3373e765f35

- Add simple tests of EvalPlanQual using the isolationtester
  infrastructure.  Much more could be done here, but at least now we
  have *some* automated test coverage of that mechanism.  In
  particular this tests the writable-CTE case reported by Phil Sorber.
  In passing, remove isolationtester's arbitrary restriction on the
  number of steps in a permutation list.  I used this so that a single
  spec file could be used to run several related test scenarios, but
  there are other possible reasons to want a step series that's not
  exactly a permutation.  Improve documentation and fix a couple other
  nits as well.
  http://git.postgresql.org/pg/commitdiff/759d9d67695783f6d04a85aba383a41c5382548c

- Fix handling of init_plans list in inheritance_planner().  Formerly
  we passed an empty list to each per-child-table invocation of
  grouping_planner, and then merged the results into the global list.
  However, that fails if there's a CTE attached to the statement,
  because create_ctescan_plan uses the list to find the plan
  referenced by a CTE reference; so it was unable to find any CTEs
  attached to the outer UPDATE or DELETE.  But there's no real reason
  not to use the same list throughout the process, and doing so is
  simpler and faster anyway.  Per report from Josh Berkus of "could
  not find plan for CTE" failures.  Back-patch to 9.1 where we added
  support for WITH attached to UPDATE or DELETE.  Add some regression
  test cases, too.
  http://git.postgresql.org/pg/commitdiff/4ec6581c0cdddfda767641f535116ee9a0412149

- Update statement about sorting of character-string data.  The sort
  order is no longer fixed at database creation time, but can be
  controlled via COLLATE.  Noted by Thomas Kellerer.
  http://git.postgresql.org/pg/commitdiff/17d3233e1bfd9fbe856f032a542f2c595e79ca01

- Add caution about multiple unique indexes breaking plpgsql upsert
  example.  Per Phil Sorber, though I didn't use his wording exactly.
  http://git.postgresql.org/pg/commitdiff/ed6e0545f5f6e9977c8410e04244138b567c5a73

- Fix pushing of index-expression qualifications through UNION ALL.
  In commit 57664ed25e5dea117158a2e663c29e60b3546e1c, I made the
  planner wrap non-simple-variable outputs of appendrel children (IOW,
  child SELECTs of UNION ALL subqueries) inside PlaceHolderVars, in
  order to solve some issues with EquivalenceClass processing.
  However, this means that any upper-level WHERE clauses mentioning
  such outputs will now contain PlaceHolderVars after they're pushed
  down into the appendrel child, and that prevents indxpath.c from
  recognizing that they could be matched to index expressions.  To
  fix, add explicit stripping of PlaceHolderVars from index operands,
  same as we have long done for RelabelType nodes.  Add a regression
  test covering both this and the plain-UNION case (which is a totally
  different code path, but should also be able to do it).  Per bug
  #6416 from Matteo Beccati.  Back-patch to 9.1, same as the previous
  change.
  http://git.postgresql.org/pg/commitdiff/b28ffd0fcc583c1811e5295279e7d4366c3cae6c

- Tweak index costing for problems with partial indexes.
  btcostestimate() makes an estimate of the number of index tuples
  that will be visited based on knowledge of which index clauses can
  actually bound the scan within nbtree.  However, it forgot to
  account for partial indexes in this calculation, with the result
  that the cost of the index scan could be significantly overestimated
  for a partial index.  Fix that by merging the predicate with the
  abbreviated indexclause list, in the same way as we do with the full
  list to estimate how many heap tuples will be visited.  Also,
  slightly increase the "fudge factor" that's meant to give preference
  to smaller indexes over larger ones.  While this is applied to all
  indexes, it's most important for partial indexes since it can be the
  only factor that makes a partial index look cheaper than a similar
  full index.  Experimentation shows that the existing value is so
  small as to easily get swamped by noise such as
  page-boundary-roundoff behavior.  I'm tempted to kick it up more
  than this, but will refrain for now.  Per report from Ruben Blanco.
  These are long-standing issues, but given the lack of prior
  complaints I'm not going to risk changing planner behavior in back
  branches by back-patching.
  http://git.postgresql.org/pg/commitdiff/21a39de5809cd3050a37d2554323cc1d0cbeed9d

- Fix typo in comment.  Peter Geoghegan
  http://git.postgresql.org/pg/commitdiff/dd243b3e40c24cd7c6b0db80bb39061f8f85af7b

- Assorted comment fixes, mostly just typos, but some obsolete
  statements.  YAMAMOTO Takashi
  http://git.postgresql.org/pg/commitdiff/ad10853b30b84d89905e023afa599de3a1fea4c6

Peter Eisentraut pushed:

- Remove quotes around format_type_be() output.  format_type_be()
  takes care of any needed quoting itself.
  http://git.postgresql.org/pg/commitdiff/89dda5f2979fbe277809369ff88832ab39e83ff0

- Do not access indclass through Form_pg_index.  Normally, accessing
  variable-length members of catalog structures past the first one
  doesn't work at all.  Here, it happened to work because indnatts was
  checked to be 1, and so the defined FormData_pg_index layout, using
  int2vector[1] and oidvector[1] for variable-length arrays, happened
  to match the actual memory layout.  But it's a very fragile
  assumption, and it's not in a performance-critical path, so code it
  properly using heap_getattr() instead.  bug analysis by Tom Lane
  http://git.postgresql.org/pg/commitdiff/8a3f745f160d8334ad978676828d3926ac949f43

- Hide most variable-length fields from Form_pg_* structs.  Those
  fields only appear in the structs so that genbki.pl can create the
  BKI bootstrap files for the catalogs.  But they are not actually
  usable from C.  So hiding them can prevent coding mistakes, saves
  stack space, and can help the compiler.  In certain catalogs, the
  first variable-length field has been kept visible after manual
  inspection.  These exceptions are noted in C comments.  reviewed by
  Tom Lane
  http://git.postgresql.org/pg/commitdiff/8137f2c32322c624e0431fac1621e8e9315202f9

- Disallow ALTER DOMAIN on non-domain type everywhere.  This has been
  the behavior already in most cases, but through omission, ALTER
  DOMAIN / OWNER TO and ALTER DOMAIN / SET SCHEMA would silently work
  on non-domain types as well.
  http://git.postgresql.org/pg/commitdiff/27874583627e049a049dc1327deb12a02a7013ab

- Revert unfortunate whitespace change.  In
  e5e2fc842c418432756d8b5825ff107c6c5fc4c3, blank lines were removed
  after a comment block, which now looks as though the comment refers
  to the immediately following code, but it actually refers to the
  preceding code.  So put the blank lines back.
  http://git.postgresql.org/pg/commitdiff/bf90562aa464e3a9afedde5f0007058f381d00fe

- Show default privileges in information schema.  Hitherto, the
  information schema only showed explicitly granted privileges that
  were visible in the *acl catalog columns.  If no privileges had been
  granted, the implicit privileges were not shown.  To fix that, add
  an SQL-accessible version of the acldefault() function, and use that
  inside the aclexplode() calls to substitute the catalog-specific
  default privilege set for null values.  reviewed by Abhijit
  Menon-Sen
  http://git.postgresql.org/pg/commitdiff/b376ec6fa57bc76037014ede29498e2d1611968e

Alvaro Herrera pushed:

- Add pg_trigger_depth() function.  This reports the depth level of
  triggers currently in execution, or zero if not called from inside a
  trigger.  No catversion bump in this patch, but you have to initdb
  if you want access to the new function.  Author: Kevin Grittner
  http://git.postgresql.org/pg/commitdiff/74ab96a45ef6259aa6a86a781580edea8488511a

- Have \copy go through SendQuery.  This enables a bunch of features,
  notably ON_ERROR_ROLLBACK.  It also makes COPY failure (either in
  the server or psql) as a whole behave more sanely in psql.
  Additionally, having more commands in the same command line as COPY
  works better (though since psql splits lines at semicolons, this
  doesn't matter much unless you're using -c).  Also tighten a couple
  of switches on PQresultStatus() to add PGRES_COPY_BOTH support and
  stop assuming that unknown statuses received are errors; have those
  print diagnostics where warranted.  Author: Noah Misch
  http://git.postgresql.org/pg/commitdiff/08146775acd8bfe0fcc509c71857abb928697171

Magnus Hagander pushed:

- Track temporary file count and size in pg_stat_database.  Add
  counters for number and size of temporary files used for
  spill-to-disk queries for each database to the pg_stat_database
  view.  Tomas Vondra, review by Magnus Hagander
  http://git.postgresql.org/pg/commitdiff/bc3347484a7bf9eddb98e4352d84599cae9a31c6

- Add deadlock counter to pg_stat_database.  Adds a counter that
  tracks number of deadlocks that occurred in each database to
  pg_stat_database.  Magnus Hagander, reviewed by Jaime Casanova
  http://git.postgresql.org/pg/commitdiff/61cb8c5abb9235c3106af6c6a6e60d94cb1eee80

- Fix a copy/pasted typo in several comments
  http://git.postgresql.org/pg/commitdiff/7729e22d83b31afa1009f190bf0f4838cc8feaf8

- Fix wording, per Peter Geoghegan
  http://git.postgresql.org/pg/commitdiff/c9f14bb4acf3e5caff97ef0a639c3ee911932e1c

- Prevent logging "failed to stat file: success" for temp files.  This
  was broken in commit bc3347484a7bf9eddb98e4352d84599cae9a31c6, the
  addition of statistics counters for temp files.  Reported by Thom
  Brown
  http://git.postgresql.org/pg/commitdiff/672614cf2137b2a3778c69de8d73770d84790e44

Heikki Linnakangas pushed:

- Make bgwriter sleep longer when it has no work to do, to save
  electricity.  To make it wake up promptly when activity starts
  again, backends nudge it by setting a latch in MarkBufferDirty().
  The latch is kept set while bgwriter is active, so there is very
  little overhead from that when the system is busy. It is only armed
  before going into longer sleep.  Peter Geoghegan, with some changes
  by me.
  http://git.postgresql.org/pg/commitdiff/6d90eaaa89a007e0d365f49d6436f35d2392cfeb

- Fix sentence in docs: checkpoints are not done by bgwriter anymore.
  http://git.postgresql.org/pg/commitdiff/d4bad4e1e1c7269b906f3b005fc322537630efcf

- Mention in the docs that bgwriter now sleeps longer when it has no
  work to do.
  http://git.postgresql.org/pg/commitdiff/2e92b5872faeb01f1865bb00556ec7be0ef006ee

- Fix copy-paste error in docs.  Dean Rasheed
  http://git.postgresql.org/pg/commitdiff/59c67ecdd39725aaee0db6e09f399c8e6c248f22

- Initialize the new bgwriterLatch field properly.  Peter Geoghegan
  http://git.postgresql.org/pg/commitdiff/cf3fff6326299deca77c1387df31d24aea36e2e1

== Rejected Patches (for now) ==

No one was disappointed this week 

== Pending Patches ==

Noah Misch sent in another revision of the patch to collect statistics
for arrays.

Jim Mlodgensky and Heikki Linnakangas traded patches to add a new GUC
for welcome messages.

Matthew Draper sent in another revision of the patch to enable SQL
language functions to reference parameters by name.

Simon Riggs sent in another revision of the patch to have a WAL
restore process during recovery.

Simon Riggs sent in another revision of the freelist_wait_stats patch.

Alexander Korotkov and Jeff Davis traded patches for GiST indexing on
range types.

Alvaro Herrera sent in two more revisions of the FOREIGN KEY LOCK
patch.

Jaime Casanova sent in another revision of the relation_free_space
patch.

Thomas Ogrisegg sent in a patch intended to fix a bug in
pg_basebackup, which exits with 0 even if it had errors while writing
the backup to disk when the backup file is to be sent to stdout.

Fujii Masao sent an add-on patch to the one which adds a "write"
synchrounous replication mode to modify postgresql.conf appropriately.

Noah Misch sent in another revision of the patch to prevent unneeded
table rewrites in certain types of ALTER TABLE...ALTER TYPE
operations.

Heikki Linnakangas sent in two more revisions of the GROUP COMMIT
patch, reviews by Robert Haas, Jeff Janes and Jesper Krogh.

Dimitri Fontaine sent in another revision of the patch to add triggers
to commands in general.

Abhijit Menon-Sen and Pavel Stehule traded revisions of a patch to
allow better debugging of overloaded functions.

Abhijit Menon-Sen sent in a patch atop Andrew Dunstan's patch to add
{query,array,row}-to-json functionality.

KaiGai Kohei sent in another revision of the patch to plug certain
types of information leaks in views.

Abhijit Menon-Sen sent in a patch to fix some infelicities in Peter
Eisentraut's patch to enable using \0 as a field or record separator.

Jaime Casanova sent in another revision of the patch to add a
pg_stats_recovery view.

Abhijit Menon-Sen sent in a fix to Daniel Farina's patch which factors
out the various crc32 implementations in the code base.

Kyotaro HORIGUCHI sent in another revision of the patch to add a new
libpq tuple storage and use same to speed up dblink.  Reviews by Marko
Kreen and Merlin Moncure.

Peter Geoghegan sent in another revision of the fast path sort patch.

Marti Raudsepp sent in another revision of the patch to cache stable
expressions with constant arguments.

Luben Karavelov sent in a patch to enable limited cover density
ranking in text search.  Reviews by Oleg Bartunov and Sushant Sinha.

Dan Scales sent in another WIP patch implementing double-write with
the suggested double-write buffers per feedback from Heikki
Linnakangas and Simon Riggs.

Jeff Janes sent in a patch to allow simulating log contention in
pg_bench.

Dean Rasheed sent in a patch to fix a performance regression in
index-only scans.

Petr (PJMODOS) Jelinek sent in another revision of the patch to enable
CHECK FUNCTION.

Simon Riggs sent in another revision of the DROP INDEX CONCURRENTLY
patch.

Simon Riggs sent in another revision of the patch intended to reduce
CLOG contention.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

               pgsql-announce-unsubscribe <at> postgresql.org

PGCon 2012 Call for Papers - extension

We apologize that http://www.bsdcan.org/ was offline for 12 hours from early Sunday morning.

The deadline for submissions has been extended to Tuesday 31 January.

PGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of
Ottawa.  It will be preceded by two days of tutorials on 15-16 May 2012.

We are now accepting proposals for talks.  Proposals can be quite 
simple. We do not require academic-style papers.

If you are doing something interesting with PostgreSQL, please submit
a proposal.  You might be one of the backend hackers or work on a
PostgreSQL related project and want to share your know-how with
others. You might be developing an interesting system using PostgreSQL
as the foundation. Perhaps you migrated from another database to
PostgreSQL and would like to share details.  These, and other stories
are welcome. Both users and developers are encouraged to share their
experiences.

Here are a some ideas to jump start your proposal process:

- novel ways in which PostgreSQL is used
- migration of production systems from another database
- data warehousing
- tuning PostgreSQL for different work loads
- replication and clustering
- hacking the PostgreSQL code
- PostgreSQL derivatives and forks
- applications built around PostgreSQL
- benchmarking and performance engineering
- case studies
- location-aware and mapping software with PostGIS
- The latest PostgreSQL features and features in development
- research and teaching with PostgreSQL
- things the PostgreSQL project could do better
- integrating PostgreSQL with 3rd-party software

Both users and developers are encouraged to share their experiences.

The schedule is:

8 Jan 2012 Proposal acceptance begins
31 Jan 2012 Proposal acceptance ends
19 Feb 2012 Confirmation of accepted proposals

See also <http://www.pgcon.org/2012/papers.php>

Instructions for submitting a proposal to PGCon 2012 are available
from: <http://www.pgcon.org/2012/submissions.php>

--

-- 
Dan Langille - http://langille.org

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

               pgsql-announce-unsubscribe <at> postgresql.org

PG Day France 2012 : Call for papers

====== PG Day France: Call for papers ======

PG Day France is a major French-speaking PostgreSQL community event.
This year the conference will be held on Thursday, June 7th in Lyon. A
hundred visitors are expected for this day dedicated to PostgreSQL and
its associated projects.

You can find more information at: http://www.pgday.fr

Are you an expert in a field related to free databases? Do you use
PostgreSQL in a specific context (high-volume, high load, innovative
projects, etc.)? Do you participate in free projects linked to
PostgreSQL? If so, do not hesitate to propose a talk!

For this 2012 edition, the highlighted topics are:

  *  Administration of large databases
  *  High-availability and load balancing
  *  Data security
  *  Case studies / Testimonials
  *  Optimization
  *  Tests, benchmarks, hardware, etc.
  *  Data warehouses and BI systems

This list is not exhaustive; you may propose other topics related to
PostgreSQL.

PG Day France is oriented toward professionals, including IT managers,
policy makers, project managers, database administrators, developers,
system administrators and all the profiles that come into contact with a
DBMS.

To submit a talk, simply send an e-mail to
propositions-pgdayfr2012 <at> postgresql.fr, stating the following:

  * Your full name;
  * Your company / employer;
  * Your twitter account (optional);
  * The title of your talk;
  * The length of your presentation (45 minutes max. questions included);
  * A short description (200 characters max.)
  * A long description (700 characters max.)
  * A photo (200 x 200 pixels minimum).

Talks should be in French. Please note that your speech may be captured
in audio/video and broadcast on the Internet.

The deadline for sending proposals is Saturday, February 25, 2012 at
23:59 CEST.

During the month of March 2012, a preliminary vote will be held within
the French-speaking community to assess the various proposals.

Then the selection committee will review all valid proposals. The choice
of talks will be based on the quality of the paper, its interest to a
professional audience, the coherence with the overall schedule of the
day and the outcome of the preliminary vote. The decision of the
Selection Committee shall be final and binding.

The program committee consists of:
  * Gautier Di Folco (Student, INSA Lyon)
  * Vik Fearing (Developer, Auriga)
  * Guillaume Lelarge (CTO, Dalibo)
  * Ludovic Levesque (CTO, Fotolia)
  * Vincent Picavet (Co-founder, Oslandia)
  * Thomas Reiss (DBA, Ministry of Interior)

Committee members act on their own behalf; their choices do not
necessarily reflect those of their employer.

The selected speakers will be notified by e-mail by March 17, 2012, the
day of the announcement of the program.

For questions about this call for papers and PG Day France in general,
you can send a message to: pgdayfr2012 <at> listes.postgresql.fr

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

               pgsql-announce-unsubscribe <at> postgresql.org

PGDay NYC 2012 - Call for Papers + Registration

EnterpriseDB Releases Postgres Plus Cloud Database

CloudBees, Engine Yard to Include Postgres Plus Cloud Database as Part
of their Cloud Services Offering

EnterpriseDB, the leading worldwide provider of PostgreSQL and Oracle
database compatibility products and services, today announced the
general availability of Postgres Plus® Cloud Database on Amazon Web
Services.  Postgres Plus Cloud Database is a full-featured,
enterprise-class PostgreSQL database-as-a-service (DBaaS).
EnterpriseDB also announced today that CloudBees and Engine Yard have
selected Postgres Plus Cloud Database as one of their leading database
solutions.

Postgres Plus Cloud Database dramatically simplifies the setup and
configuration of PostgreSQL in the cloud.  In addition to support for
Amazon EC2, EnterpriseDB has worked with HP to ensure Postgres Plus
Cloud Database will run well with HP Cloud Compute.  HP Cloud Compute
currently leverages the OpenStack Nova compute platform and API.

"Postgres Plus Cloud Database is the only solution on the market today
that makes deploying new instances of PostgreSQL or Postgres Plus
Advanced Server easy in any environment,” said Ed Boyajian, President
and CEO of EnterpriseDB.  “And, through our partnerships with industry
leaders CloudBees, Engine Yard, HP and OpenStack, customers will have
numerous ways to take advantage of PostgreSQL ‘elastically’ on
multiple cloud platforms.”

Postgres Plus Cloud Database combines the advantages of cloud
computing with the features expected in an enterprise-class database,
including:

* Fully ACID compliant relational database service
* Point-and-click simple setup & management with web-based interface
* Automatic scaling, load balancing and failover
* Automated online backup and point-in-time recovery
* Database Cloning
* Oracle database compatibility
* Postgres Plus Cloud Database is available now with two versions of
its cloud database:  PostgreSQL 9.1, and Postgres Plus Advanced Server
9.0. Pricing for Postgres Plus Cloud Database on Amazon Web Services
is the same as Amazon RDS (MySQL), whether you choose the PostgreSQL
or Postgres Plus Advanced Server database engine.

On January 26th at 9:00 AM PT Ed Boyajian, President and CEO at
EnterpriseDB, will host a live Postgres Plus Cloud Database Launch
Event and demo.  To register, visit
http://cloud.enterprisedb.com/launch-event.  To try Cloud Database for
yourself or participate in a free trial visit:
http://cloud.enterprisedb.com

Please join us for our live Twitter chat on January 30th at 10:00 AM
PT where Karen Tegan Padir, EVP of Products and Engineering at
EnterpriseDB will answer your questions about Postgres Plus Cloud
Database with the hashtag #cloudDB.

Supporting quotes:

CloudBees

“With Postgres Plus Cloud Database on the CloudBees Java Platform, our
developers can easily build applications that invoke a truly elastic
database knowing that Postgres is always backed up and available, but
without the hassles of database administration,” said Sacha Labourey,
CEO and Founder of CloudBees.  “Plus, EnterpriseDB and CloudBees both
provide innovative, cloud-based scale-out architectures, which are
expected in premier database and application platforms.”

Engine Yard

“We’re very pleased to have EnterpriseDB offer Postgres Plus Cloud
Database to developers running apps on Engine Yard Cloud,” said Mike
Piech, VP, Product Management and Marketing at Engine Yard. “Postgres
Plus Cloud Database will enable our mutual customers to provision both
multi-host PostgreSQL and Postgres Plus Advanced Server clusters
easily and efficiently.”

Red Hat

“Elasticity and horizontal scaling are critical characteristics for
cloud applications, which make Postgres Plus even more attractive for
applications in the cloud,” said Brian Stevens, CTO and VP, Worldwide
Engineering at Red Hat. “As a leading provider of cloud platforms and
infrastructure, we are excited to see enhanced innovation and choice
for cloud developers and users.”

451 Research

“We have recently seen a surge of interest in PostgreSQL driven by its
potential for deployment in the cloud,” said Matt Aslett, Research
Manager, Data Management and Analytics, 451 Research.  “With the
addition of auto-data size elasticity and horizontal scaling in
Postgres Plus Cloud Database, EnterpriseDB has re-introduced
PostgreSQL as a database platform for the creation and delivery of
private, public and hybrid cloud services, as opposed to simply a
database running in the cloud.”

Voices Heard Media

“We needed a low touch solution that was easy to use and could
elastically scale PostgreSQL in the cloud,” said Mark Baird, Director
of IT at Voices Heard Media. “Tasks such as load balancing,
auto-scaling of the cluster, auto backup and auto-failover can be
extremely difficult to get configured correctly, but with Postgres
Cloud Database you get all of this right out of the box.”

Aquent

“With Postgres Plus Cloud Database, EnterpriseDB brings a welcome
addition to cloud-based services,” said Larry Bolick, CIO, Aquent.
“As satisfied customers of EnterpriseDB for the past two years, we
have been running Postgres Plus Advanced Server on virtual servers
worldwide and have been eagerly awaiting a version available natively
in the cloud.”

Burris Logistics

“With Postgres Plus Cloud Database, EnterpriseDB changes how we should
think about database services in the cloud.  Their solution has
reduced much of the admin effort, and all of the infrastructure work
out of database installation and configuration. It almost seems too
easy,” said Ed Krupka, CIO, Burris Logistics. “Postgres Plus Cloud
Database is so innovative, especially with its auto-data size
elasticity and horizontal scaling. It’s poised to make PostgreSQL the
de facto database for the cloud.”

Connect with EnterpriseDB

Learn more about EnterpriseDB
Read the blog: http://blogs.enterprisedb.com/

Follow us on Twitter: http://www.twitter.com/enterprisedb

Become a fan on Facebook: http://www.facebook.com/EnterpriseDB?ref=ts

Join us on Google+: https://plus.google.com/108046988421677398468

About EnterpriseDB Corporation

EnterpriseDB, the Enterprise PostgreSQL Company, provides
enterprise-class PostgreSQL products and PostgreSQL services to help
IT organizations be successful with the world's most advanced open
source database. The company’s Postgres Plus products are ideally
suited for transaction-intensive applications requiring superior
performance, massive scalability and compatibility with proprietary
database products to reduce overall database costs. EnterpriseDB has
offices in North America, Europe and Asia. The company was founded in
2004 and is headquartered in Bedford, MA. For more information, please
call +1-781-357-3390 or visit www.enterprisedb.com.

---------------------------(end of broadcast)---------------------------
-To unsubscribe from this list, send an email to:

               pgsql-announce-unsubscribe <at> postgresql.org