Noticias relacionadas con PostgreSQL

PgConf.Russia 2017

Eventos PostgreSQL [ENG] - Mié, 15/03/2017 - 01:00

The next Russian PostgreSQL conference will take place in Moscow Digital October Center on March 15-17, 2017 - one day of tutorials and two days of talks in three parallel sessions.

dbMigration .NET v5 released

Noticias PostgreSQL [ENG] - Vie, 10/03/2017 - 01:00

dbMigration .NET v5 is a simple, easy and intuitive multiple database migration and sync tool, With it you can easily migrate schema and data between different databases without complicated procedures.

Supported databases: PostgreSQL, SQL Server, SQL Azure, LocalDB, MySQL, Oracle, IBM DB2, Informix, Vertica, NuoDB, Teradata, Sybase ASE, Firebird, SQLite, SQLCe, VistaDB, Access, dBase, FoxPro, Text, Excel, ODBC, OleDB...etc.

Free, All-In-One, Portable, Single executable file and Multi-language.

Major New features from version 3.8 to 5.0 (2016/10/01~2017/03/10):

  • Added support for PostgreSQL <-> VistaDB migration
  • Added support for PostgreSQL error detail message
  • Added support for PostgreSQL (one/two) dimensional arrays
  • Added Multi-Language UI (Options->Language)
  • Added Automatically generate foreign keys (PG)
  • Ability to add custom delimited file extensions
  • Improved Migrating VIEWS/FUNCTIONS/SEQUENCES definitions (PG->PG)
  • Improved Data Synchronization
  • Improved Automatic Mapping Types (UDT)
  • Improved Custom Mapping Types
  • Improved Command-Line
  • Compiled with Visual Studio 2017
  • ...and more
The new version is immediately available for download.

PGConf India 2017

Eventos PostgreSQL [ENG] - Vie, 03/03/2017 - 01:00

The All India PostgreSQL UserGroup announces the PGConf India conference to be held in Bengaluru on 3rd March 2017.

As always, PGConf India is an excellent opportunity to get yourself introduced to leading PostgreSQL users, developers, and to learn about features in the latest PostgreSQL release. It also provides a platform to share experiences and to network with like-minded open source database enthusiasts.

We are thrilled to announce that Simon Riggs, Chief Technology Officer at 2ndQuadrant and hacker/committer in the PostgreSQL community will be delivering the Keynote at this event!

The CFP closes on 13th Jan 2017 and the early bird registration closes on 15th Jan 2017. More details about the event can be found at http://pgconf.in/

PostgreSQL@SCaLE15x

Eventos PostgreSQL [ENG] - Jue, 02/03/2017 - 01:00

PostgreSQL@SCaLE is a two day, two track event which takes place on March 2-3, 2017, at Pasadena Convention Center, as part of SCaLE 15X.

http://www.socallinuxexpo.org/scale/15x/cfp

JDBC 42.0.0 Released

Noticias PostgreSQL [ENG] - Lun, 20/02/2017 - 01:00

The JDBC group is proud to release a new version, and in keeping with the version renumbering meme we have released version 42.0.0.

Notable changes include:

  • Support for PostgreSQL versions below 8.2 was dropped
  • java.util.logging is now used for logging: logging documentation
  • Ensure executeBatch() can be used with pgbouncer. Previously pgjdbc could use server-prepared statements for batch execution even with prepareThreshold=0 (see issue 742)
  • Replication protocol API was added: replication API documentation, PR#550
  • Version bumped to 42.0.0 to avoid version clash with PostgreSQL version
  • Error position is displayed when SQL has unterminated literals, comments, etc (see issue 688)

Prague PostgreSQL Developer Days 2017

Eventos PostgreSQL [ENG] - Mié, 15/02/2017 - 01:00

A two-day conference, organized by Czech and Slovak PostgreSQL User Group. The conference will have two parts, as in the last few years - trainings on Feb 15 (either half or whole day sessions) and regular conference (with ~45-minute talks) on Feb 16.

Registrations now open for pgDay Asia 2017

Noticias PostgreSQL [ENG] - Mar, 14/02/2017 - 01:00

Team pgDay Asia is happy to announce that registrations for the conference are now open. For a limited time, we are offering group discounts for 3+ people. Register yourself by clicking: http://2017.pgday.asia/#registration.

Schedule for the 2-day single-track conference has also been published: http://2017.pgday.asia/#schedule

Please note that the 2nd day of the conference is part of FOSSASIA's dedicated PostgreSQL track. Tickets for FOSSASIA can be purchased separately here: http://2017.fossasia.org/tickets/

A special shout out to all our speakers and sponsors. This event is not possible without your support. For anyone wishing to sponsor, please send an email to pgday-asia@googlegroups.com.

pgDay Asia 2017 is scheduled to be held in Singapore on 17th & 18th of March. More details here: http://2017.pgday.asia/. The conference will be held along with FOSSASIA - one of the largest FOSS conference on the planet. pgDay Asia will be PostgreSQL conference series for all PostgreSQL enthusiasts in the Asia Pacific region.

PostgreSQL@SCaLE15x - March 2-3, 2017, Pasadena Convention Center

Noticias PostgreSQL [ENG] - Lun, 13/02/2017 - 01:00
Please join us at PostgreSQL@SCaLE15x!

PostgreSQL@SCaLE is an embedded PostgreSQL conference held as part of SCaLE15x on Thursday and Friday, March 2-3, 2017. We will have 24 one-hour PostgreSQL talks -- two rooms for two days. This is by far the best value for your money of any North American PostgreSQL event!

For the talk schedule, please see: We will also have a PostgreSQL community booth in the exhibition hall all weekend.

SCaLE15x (the 15th annual Southern California Linux Expo), taking place on March 2-5, 2017 at the Pasadena Convention Center, is the largest community-run open-source and free software conference in North America. It is held annually in the Los Angeles area. PostgreSQL@SCaLE is always very popular and well attended. Don't miss out!

There is a nominal registration cost, but we have a 50% discount code: PSQL

Please go register here.

PostgreSQL@SCaLE15x is made possible by the United States PostgreSQL Association, a nonprofit 501(c)(3) created to support PostgreSQL in the United States through user group development, conferences, educational initiatives, and fun. There is no way we would be able to produce PostgreSQL@SCaLE15x without the generous support of our sponsors:

2ndQuadrant Amazon Web Services Command Prompt OpenSCG PostgreSQL Consulting

We hope to see everyone there!

The PostgreSQL@SCaLE15x Committee Joe, Jim, and Gabrielle

PostgreSQL 9.6.2, 9.5.6, 9.4.11, 9.3.16 and 9.2.20 released!

Noticias PostgreSQL [ENG] - Jue, 09/02/2017 - 01:00

The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.2, 9.5.6, 9.4.11, 9.3.16, and 9.2.20. This release includes fixes that prevent data corruption issues in index builds and in certain write-ahead-log replay situations, which are detailed below. It also patches over 75 other bugs reported over the last three months.

Users should plan to apply this update at the next scheduled downtime.

Build corruption with CREATE INDEX CONCURRENTLY

There existed a race condition if CREATE INDEX CONCURRENTLY was called on a column that had not been indexed before, then rows that were updated by transactions running at the same time as the CREATE INDEX CONCURRENTLY command could have been indexed incorrectly.

If you suspect this may have happened, the most reliable solution is to rebuild affected indexes after installing this update.

This issue is present in the 9.2, 9.3, 9.4, 9.5, and 9.6 series of PostgreSQL.

Fixes for visibility and write-ahead-log stability

This release contains several fixes to improve the stability of visible data and WAL logging that we wish to highlight here.

Prior to this release, data could be prematurely pruned by a vacuum operation when a special snapshot used for catalog scans was presently available. Specifically, the vacuum operation would not be aware of the oldest xmin for this special snapshot. The error would surface with a message such as:

"cache lookup failed for relation 1255"

This release ensures that vacuum operations will account for the catalog scan snapshots.

Additionally, there are several fixes to improved the stability of write-ahead-logging, including:

  • A fix for BRIN index WAL logging where a replay could make a portion of the BRIN index useless and require recomputing
  • A fix for an unlogged table where a WAL-log would be created under the "wal_level = minimal" setting, and upon replay after crash, the table would not appear to be properly reset
  • A fix in the WAL page header validation when re-reading segments that fixes the error of "out-of-sequence TLI" that could be reported during recovery

These issues are present in the 9.6 series of PostgreSQL releases and may also be present in the 9.2, 9.3, 9.4, and 9.5 series.

Bug Fixes and Improvements

This update also fixes a number of bugs reported in the last few months. Some of these issues affect only the 9.6 series, but many affect all supported versions. There are more than 75 fixes provided in this release, including:

  • Several fixes for operating in hot standby mode
  • Disallow setting the num_sync field to zero in synchronous_standby_names
  • Don't count background worker processes against a user's connection limit
  • Fix check for when an extension member object can be dropped
  • Fix tracking of initial privileges for extension member objects so that it works correctly with ALTER EXTENSION ... ADD/DROP
  • Several vacuum and autovacuum fixes
  • Fix CREATE OR REPLACE VIEW to update the view query before attempting to apply the new view options
  • Make sure ALTER TABLE preserves index tablespace assignments when rebuilding indexes
  • Several fixes to the query planner, including fixes for foreign tables and CTEs
  • Several fixes around the full-text search feature to improve accuracy and performance of the search
  • Several fixes and performance improvements in several array functions
  • Several fixes around the interaction of foreign-key constraints with trigger functions around specific ALTER TABLE operations
  • Remove optimizations for date/time data types that returned incorrect data
  • Fix incorrect use of view reloptions as regular table reloptions
  • Fix incorrect "target lists can have at most N entries" complaint when using ON CONFLICT with wide tables
  • Fix spurious "query provides a value for a dropped column" errors during INSERT or UPDATE on a table with a dropped column
  • Prevent multicolumn expansion of foo.* in an UPDATE source expression
  • Ensure that column typmods are determined accurately for multi-row VALUES constructs
  • Several fixes for the psql command-line tool
  • Prevent multiple calls of pg_start_backup() and pg_stop_backup() from running concurrently
  • Several fixes for pg_dump, pg_restore, and pg_basebackup, including a possible pg_basebackup failure on standby server when including WAL files
  • Several fixes for parallel workers and plans for parallel queries including fixing a crash if the number of workers available to a parallel query decreases during a rescan
  • Several fixes to PL/pgSQL, PL/Python, and PL/Tcl
  • Several fixes for contrib modules
  • Allow DOS-style line endings in ~/.pgpass files, even on Unix

Update time zone data files to tzdata release 2016j for DST law changes in northern Cyprus (adding a new zone Asia/Famagusta), Russia (adding a new zone Europe/Saratov), Tonga, and Antarctica/Casey. Historical corrections for Italy, Kazakhstan, Malta, and Palestine. Switch to preferring numeric zone abbreviations for Tonga.

Updating

All PostgreSQL update releases are cumulative. As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shut down PostgreSQL and update its binaries.

If you believe you have been affected by the aforementioned CREATE INDEX CONCURRENTLY bug, you will have to rebuild the index. Here is an example of how to rebuild an index in a production system without losing the ability to utilize the index:

CREATE INDEX CONCURRENTLY new_index_name ON table_name (column_name); DROP INDEX CONCURRENTLY old_index_name; ALTER INDEX new_index_name RENAME TO old_index_name;

Note that using this method means you will briefly have two copies of the same index, so if disk space is an issue you may need to take other approaches.

Users who have skipped one or more update releases may need to run additional, post-update steps; please see the release notes for earlier versions for details.

Links:

SQL Multi Select for PostgreSQL released

Noticias PostgreSQL [ENG] - Lun, 06/02/2017 - 01:00

Yohz Software has released SQL Multi Select for PostgreSQL, an invaluable too to add to your toolkit if you manage multiple PostgreSQL servers.

SQL Multi Select runs multiple scripts on multiple servers with a single click.

Say you want to find out the 5 largest tables in each database, on each of your 20 PostgreSQL servers. All you have to do is:

  • select the appropriate query group (you can define as many as you want, each containing a different set of servers)
  • load the script from disk (you can run as many scripts as you want)
  • run the project, and you're done! The results are returned in a single consolidated result set for easy comparison and analysis.

Imagine how SQL Multi Select can help you do your work faster. Need to create a new user account on a set of servers? Just select the appropriate query group, write the script, and run the project. Need to create a new database on a bunch of servers? Prepare the CREATE DATABASE script, select a query group, run the script, and you’re done. The possibilities are endless.

System requirements:

  • Runs on Windows XP to Windows 10.
  • Supports PostgreSQL 8.3 to 9.6, without the need for any additional database drivers.

For more information about SQL Multi Select for PostgreSQL, please visit http://www.yohz.com/sms_details.htm, or download a free 14-day trial.

About Yohz Software

Yohz Software is a developer of database applications for most popular database engines. Learn more about Yohz Software at http://www.yohz.com.

FOSDEM PGDay 2017

Eventos PostgreSQL [ENG] - Vie, 03/02/2017 - 01:00

PostgreSQL Europe will host a separate PGDay as well as a developer room during FOSDEM 2017.

pgwatch2: PostgreSQL monitoring has never been easier before

Noticias PostgreSQL [ENG] - Mar, 31/01/2017 - 01:00
pgwatch 2: PostgreSQL monitoring made easy

Cybertec Schönig & Schönig GmbH proudly presents pgwatch 2 - the most easy to install monitoring tool for PostgreSQL ever released.

It is based on Grafana and offers out of the box monitoring for PostgreSQL databases. Due to the use of containers, pgwatch 2 can be installed in minutes without having to worry about dependencies and complex installation procedures. It is pre-configured. All it needs is a database connection and you are ready to go.

Fire it up and pgwatch will already collect data and display vital information for you in no time.

pgwatch 2 is Open Source can be used free of charge.

Please share feedback as we will improve pgwatch based on your ideas.

More information can be found on our website

Follow us on twitter @PostgresSupport and share your feedback.

pgBadger v9.1 has been released

Noticias PostgreSQL [ENG] - Vie, 27/01/2017 - 01:00

Paris, France - January 24th, 2017

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

pgBadger 9.1 was released today, this is a maintenance release that fix some minor bugs. There is also a new report on error class distribution and some feature enhancements:

  • Add report of error class distribution when SQLState is available in the log_line_prefix (see %e placeholder).
  • Update SQL Beautifier to pgFormatter v1.6 code.
  • Improve error message normalization.
  • Add --normalized-only option to generate a text file containing all normalized queries found in a log with count.
  • Allow %c (session id) to replace %p (pid) as unique session id.
  • Add waiting for lock messages to event reports.
  • Add --start-monday option to start calendar weeks in Monday instead of default to Sunday.

Here are the complete list of changes:

  • Add report of error class distribution when SQLState is available in the log line prefix. Thanks to jacks33 for the feature request.
  • Fix incremental global index on resize. Thanks to clomdd for the report.
  • Fix command tag log_line_prefix placeholder %i to allow space character.
  • Fix --exclude-line options and removing of obsolete directory when retention is enabled and --noreport is used.
  • Fix typo in "vacuum activity table". Thanks to Nicolas Gollet for the patch.
  • Fix autovacuum report. Thanks to Nicolas Gollet for the patch.
  • Fix author of pgbadger's logo - Damien Cazeils and English in comments. Thanks to Thibaut Madelaine for the patch.
  • Add information about pgbouncer log format in the -f option. Thanks to clomdd for the report.
  • Add --normalized-only information in documentation.
  • Fix broken report of date-time introduced in previous patch.
  • Fix duration/query association when log_duration=on and log_statement=all. Thanks to Eric Jensen for the report.
  • Fix normalization of messages about advisory lock. Thanks to Thibaut Madelaine for the report.
  • Fix report of auto_explain output. Thanks to fch77700 for the report.
  • Fix unwanted log format auto detection with log entry from stdin. Thanks to Jesus Adolfo Parra for the report.
  • Add left open parentheses to the "stop" chars of regex to look for db client in the prefix to handle the PostgreSQL client string format that includes source port. Thanks to Jon Nelson for the patch.
  • Fix some spelling errors. Thanks to Jon Nelson for the patch.
  • Allow %c (session id) to replace %p (pid) as unique session id. Thanks to Jerryliuk for the report.
  • Allow pgBadger to parse default log_line_prefix that will be probably used in 10.0: '%m [%p] '
  • Fix missing first line with interpreter call.
  • Fix missing Avg values in CSV report. Thanks to Yosuke Tomita for the report.
  • Fix error message in autodetect_format() method.
  • Add --start-monday option to start calendar weeks in Monday instead of default to Sunday. Thanks to Joosep Mae for the feature request.
  • Fix --histo-average option. Thanks to Yves Martin for the report.
  • Remove plural form of --ssh-option in documentation. Thanks to mark-a-s for the report.
  • Fix --exclude-time filter and rewrite code to skip unwanted line as well code to update the progress bar. Thanks to Michael Chesterton for the report.
  • Fix support to %r placeholder in prefix instead of %h.
Links & Credits

DALIBO would like to thank the developers who submitted patches and the users who reported bugs and feature requests.

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 : https://github.com/dalibo/pgbadger/releases/
  • Mailing List : https://groups.google.com/forum/?hl=fr#!forum/pgbadger (pgbadger@googlegroups.com)

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

Inaugural meeting of pgCMH

Eventos PostgreSQL [ENG] - Mar, 24/01/2017 - 01:00

Please join fellow Central OH-based PostgreSQL enthusiasts for the first ever mtg of the newly formed PUG, pgCMH!

DB Doc 3.5 for PostgreSQL released

Noticias PostgreSQL [ENG] - Jue, 12/01/2017 - 01:00

Yohz Software has released a new version of DB Doc for PostgreSQL - a PostgreSQL schema documentation tool.

The latest version is 3.5, and includes the following changes:

  • Users can now choose which schemas to generate documentation for.
  • A warning is now raised when sequence properties cannot be read, allowing the export process to continue
  • Bug fix - function arguments raising errors.
  • Bug fix - PDF output causing out of range errors.

What DB Doc can do for PostgreSQL users:

  • Create documents in HTML, CHM, PDF, and MS Word formats
  • Eliminate tedious and time-consuming manual documentation tasks.
  • Satisfy audit requirements by keeping complete and timely documentation.
  • Document a database in a couple of clicks.
  • View inter-object and inter-database dependencies in your documents.
  • Document layouts can be fully customizable to suit your requirements.
  • Keep teams up to date by distributing documentation.

System requirements:

  • Runs on Windows XP to Windows 10.
  • Runs on Wine, so you can use DB Doc on your favorite Linux distribution.
  • Supports PostgreSQL 8.3 to 9.6, without the need for any additional database drivers.

For more information about DB Doc for PostgreSQL, please visit http://www.yohz.com/dbdoc_details.htm, and download a free 30-day trial.

About Yohz Software

Yohz Software is a developer of database applications for most popular database engines. Learn more about Yohz Software at http://www.yohz.com.

Announcing The Release Of repmgr 3.3

Noticias PostgreSQL [ENG] - Vie, 06/01/2017 - 01:00

Oxford, United Kingdom - January 6, 2017

2ndQuadrant is proud to announce the release of repmgr version 3.3, the popular tool for PostgreSQL failover since 2010.

repmgr 3.3 provides a number of usability improvements for the repmgr command line utility, particularly for the ‘standby clone’ and ‘standby register’ commands. These changes are primarily aimed at making repmgr easier to use when provisioning complex replication clusters.

repmgrd users should take note of the changes to repmgr logging behaviour.

From repmgr 3.3, support for the upcoming PostgreSQL 10 release will be provided as far as possible. PostgreSQL 10 is still under development with significant changes expected to the implementation of replication functionality; anyone wishing to test repmgr with PostgreSQL 10 should build from the repmgr master branch. Links

repmgr is an open source package that helps DBAs and System Administrators manage a cluster of PostgreSQL databases. By taking advantage of the Hot Standby capability introduced in PostgreSQL 9, repmgr greatly simplifies the process of setting up and managing databases with high availability and scalability requirements.

repmgr is distributed under GPL v3 and maintained by 2ndQuadrant.

Barman v2.1 Announced

Noticias PostgreSQL [ENG] - Jue, 05/01/2017 - 01:00

2ndQuadrant announces the release of Barman version 2.1, a Backup and Recovery Manager for PostgreSQL.

This minor release fixes a few bugs. It also introduces the --archive option to the switch-xlog command, in order to help users during the installation process of a new server.

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

Links Release notes
  • Add --archive and --archive-timeout options to switch-xlog command
  • Preliminary support for PostgreSQL 10 (#73)
  • Minor additions:
    • Add last archived WAL info to 'diagnose' output
    • Add start time and execution time to the output of 'delete' command
  • Minor bug fixes:
    • Return failure for 'get-wal' command on inactive server
    • Make 'streaming_archiver_names' and 'streaming_backup_name' options global (#57)
    • Fix rsync failures due to files truncated during transfer (#64)
    • Correctly handle compressed history files (#66)
    • Avoid de-referencing symlinks in 'pg_tblspc' when preparing recovery (#55)
    • Fix comparison of last archiving failure (#40, #58)
    • Avoid failing recovery if postgresql.conf is not writable (#68)
    • Fix output of 'replication-status' command (#56)
    • Exclude files from backups like pg_basebackup (#65, #72)
    • Exclude directories from other Postgres versions while copying tablespaces (#74)
Download About

Barman (Backup and Recovery Manager) is an open-source administration tool for disaster recovery of PostgreSQL servers written in Python. It allows your organisation to perform remote backups of multiple servers in business critical environments to reduce risk and help DBAs during the recovery phase.

Barman is distributed under GNU GPL 3 and maintained by 2ndQuadrant.

Distribuir contenido