|
|
PostgreSQL-Press related Technical Updates [Page: 8 of 66] @ TACKtech Corp. |
|
|
The JDBC group is pleased to announce the release.
Notable fixes
- ? can now be used in non-prepared statements (fixed regression of 9.4.1210)
Thanks to all of the contributors
|
|
Full View / NID: 61989 / Submitted by: The Zilla of Zuron
|
|
The PostgreSQL Magazine project is back with an original concept named The Paper Elephant :
a folded newspaper with a dynamic look & feel.

As always the content comes directly from the community ! In this first issue, we gathered articles
from key members of the PostgreSQL project: Josh Berkus talks about the new version numbering scheme,
Hans-Jürgen Schönig writes about performance and Craig Kierstens an overview of JSON, JSONB and hstore.
You'll also find an interview of Paul Ramsey from the PostGIS project.
The Paper Elephant is an independent media edited by and for the PostgreSQL Community.
This issue was created with the financial help of PostgreSQL Europe
and many benevolent contributors ( witers, editors, reviewers ). Kudos to all of them.
Just like the name says, The Paper Elephant is a "paper first" media: it is designed to be printed out
and distributed during events (conferences, meetups, etc.) to promote PostgreSQL.
The first edition will be available at PostgreSQL Conference Europe 2016,
Paris Open Source Summit 2016 and FOSDEM 2017.
If you want to distribute the magazine at a local IT event, please Contact Us !
If you want a glimpse of the newspaper, you can download the PDF version here: http://pgmag.org/download
The Paper Elephant is an open and community-driven project. Joins us at http://www.pgmag.org/contribute
|
|
Full View / NID: 61991 / Submitted by: The Zilla of Zuron
|
|
November 1, 2016: Crunchy Data is proud to announce pgBackRest 1.09, Reliable PostgreSQL Backup & Restore.
Release 1.09
Since 1.0 we have improved scalability, added backup from a standby, selective restore, and support for the 9.6 non-exclusive backup method. All the major new features since 1.0 are detailed below.
Links
New Features
Improved Multi-Processing Scalability
Converted Perl threads to child processes to improve compatibility and greatly increase scalability. 3TB/hour backup speeds can be achieved with 32 cores and 10GbE, including compression and checksums.
Backup from a Standby Cluster
Performing backups on a standby host greatly reduces CPU and IO load on the master host. pgBackRest copies the majority of the files from the standby and only a few from the master, while still producing a backup exactly as if it were performed entirely on the master.
Selective Restore
Selected databases can be restored from a cluster backup to save space when not all the databases are required. WAL replay during restore takes place for all databases so some space will be used, but generally far less than if the unneeded databases were restored completely. After recovery completes the unrestored databases will not be accessible but can be dropped in the usual way.
Non-Exclusive Backups
Support for non-exclusive backups in PostgreSQL 9.6.
Directory/File Exclusions
Exclude directories during backup that are cleaned, recreated, or zeroed by PostgreSQL at startup. These include pgsql_tmp and pg_stat_tmp. The postgresql.auto.conf.tmp file is now excluded in addition to files that were already excluded: backup_label.old, postmaster.opts, postmaster.pid, recovery.conf, recovery.done.
Exclude contents of $PGDATA/pg_replslot directory so that replication slots on the master do not become part of the backup.
Enhanced Info Command
Enhanced text output of info command to include timestamps, sizes, and the reference list for all backups.
Check Command
Added check command to validate that pgBackRest is configured correctly for archiving and backups.
Flexible Configuration
More flexible configuration for databases. Master and standby can both be configured on the backup server and pgBackRest will automatically determine which is the master. This means no configuration changes for backup are required after failing over from a master to standby when a separate backup server is used.
About
pgBackRest aims to be a simple, reliable backup and restore system that can seamlessly scale up to the largest databases and workloads. Instead of relying on traditional backup tools like tar and rsync, pgBackRest implements all backup features internally and uses a custom protocol for communicating with remote systems. Removing reliance on tar and rsync allows for better solutions to database-specific backup challenges. The custom remote protocol allows for more flexibility and limits the types of connections that are required to perform a backup which increases security.
Crunchy Data supports the ongoing and active development of pgBackRest as an entirely open source project, released under the BSD-compatible MIT license.
|
|
Full View / NID: 61990 / Submitted by: The Zilla of Zuron
|
|
Yohz Software announces the release of DB Doc 3.2 on October 24, 2016, and is available for immediate download.
Changes in this version:
- Added support for PostgreSQL 9.6
- Improved PDF and Word export progress report.
- Added tables, views, domains, sequences, and functions listing page for PDF and Word reports.
DB Doc benefits:
- 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
- Runs on Windows XP to Windows 10
- Runs in 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 details about DB Doc, visit the product page here.
|
|
Full View / NID: 61930 / Submitted by: The Zilla of Zuron
|
|
The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 v1.1. This is the second release of pgAdmin 4, and includes over 40 bug fixes and improvements. For details, please see the issue tracker roadmap.
pgAdmin 4 is a complete rewrite of pgAdmin, built using Python and Javascript/jQuery. A desktop runtime written in C++ with Qt allows it to run standalone for individual users, or the web application code may be deployed directly on a webserver for use by one or more users
through their web browser. The software has the look and feel of a desktop application whatever the runtime environment is, and vastly improves on pgAdmin III with updated user interface elements, multi-user/web deployment options, dashboards and a more modern
design.
For more information, checkout the screenshots and online documentation
pgAdmin 4 will be bundled with the EDB PostgreSQL 9.6.1 installers, or can be downloaded in source, PIP wheel, macOS or Windows packages from the pgAdmin website.
|
|
Full View / NID: 61929 / Submitted by: The Zilla of Zuron
|
|
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 9.6.1, 9.5.5, 9.4.10, 9.3.15, 9.2.19, and 9.1.24. This is also the last update for the PostgreSQL 9.1 series as it is now end-of-life. This release fixes two issues that can cause data corruption, which are described in more detail below. It also patches a number of other bugs reported over the last three months. The project urges users to apply this update at the next possible downtime.
WAL-logging of truncated relations
Prior to this release, there was a chance that a PostgreSQL instance would try to access data that no longer existed on disk. If the free space map was not updated to be aware of the truncation, a PostgreSQL database could return a page that was already truncated and produce an error such as:
ERROR: could not read block 28991 in file "base/16390/572026": read only 0 of 8192 bytes
If checksumming is enabled, checksum failures in the visibility map could also occur.
This issue is present in the 9.3, 9.4, 9.5, and 9.6 series of PostgreSQL releases.
pg_upgrade issues on big-endian machines
On big-endian machines (e.g. many non-Intel CPU architectures), pg_upgrade would incorrectly write the bytes of the visibility map leading to pg_upgrade failing to complete.
If you are using a big-endian machine (many non-Intel architectures are big-endian) and have used pg_upgrade to upgrade from a pre-9.6 release, you should assume that all visibility maps are incorrect and need to be regenerated. It is sufficient to truncate each relation's visibility map with contrib/pg_visibility's pg_truncate_visibility_map() function. Please read the "Updating" section for post-installation instructions on how to resolve this issue on your PostgreSQL instances.
This issue is present only in the PostgreSQL 9.6.0 release.
Bug Fixes and Improvements
In addition to the above, 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 50 fixes provided in this release, including:
- Fix use-after-free hazard in execution of aggregate functions using DISTINCT, which could lead to crashes
- Fix incorrect handling of polymorphic aggregates used as window functions, which could lead to crashes
- Fix incorrect creation of GIN index WAL records on big-endian machines
- Fix file descriptor leakage when truncating a temporary relation of more than 1GB
- Fix query-lifespan memory leak in a bulk UPDATE on a table with a PRIMARY KEY or REPLICA IDENTITY index
- Fix SELECT FOR UPDATE/SHARE to correctly lock tuples that have been updated by a subsequently-aborted transaction
- Fix COPY with a column name list from a table that has row-level security enabled
- Fix deletion of speculatively inserted TOAST tuples when backing out of INSERT ... ON CONFLICT
- Fix timeout length when VACUUM is waiting for exclusive table lock so that it can truncate the table
- Fix bugs in merging inherited CHECK constraints while creating or altering a table
- Fix replacement of array elements in jsonb_set()
- Fix possible sorting error when aborting use of abbreviated keys in btree indexes
- On Windows, retry creation of the dynamic shared memory control segment after an access-denied error
- Fix pgbench's calculation of average latency
- Make pg_receivexlog work correctly with --synchronous without slots
- Make pg_rewind turn off synchronous_commit in its session on the source servere
- Don't try to share SSL contexts across multiple connections in libpq
- Support OpenSSL 1.1.0
- Install TAP test infrastructure so that it's available for extension testing
- Several fixes for logical WAL decoding and replication slots
- Several fixes for minor issues in pg_dump, pg_xlogdump, and pg_upgrade
- Several fixes for minor issues in the query planner and in the output of EXPLAIN
- Several fixes for timezone support
This update also contains tzdata release 2016h for DST law changes in Palestine and Turkey, plus historical corrections for Turkey and some regions of Russia. Switch to numeric abbreviations for some time zones in Antarctica, the former Soviet Union, and Sri Lanka.
The IANA time zone database previously provided textual abbreviations for all time zones, sometimes making up abbreviations that have little or no currency among the local population. They are in process of reversing that policy in favor of using numeric UTC offsets in zones where there is no evidence of real-world use of an English abbreviation. At least for the time being, PostgreSQL will continue to accept such removed abbreviations for timestamp input. But they will not be shown in the pg_timezone_names view nor used for output.
In this update, AMT is no longer shown as being in use to mean Armenia Time. Therefore, we have changed the Default abbreviation set to interpret it as Amazon Time, thus UTC-4 not UTC+4.
EOL Notice for Version 9.1
PostgreSQL version 9.1 is now End-of-Life (EOL). No additional updates or security patches will be released by the community for this version. Users still on 9.1 are urged to upgrade as soon as possible. See our Versioning Policy (https://www.postgresql.org/support/versioning/) for more information.
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 your system was affected by the big-endian pg_upgrade bug, please read Visibility Map Problems and follow the instructions on how to fix your this issue on your PostgreSQL instances.
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:
|
|
Full View / NID: 61891 / Submitted by: The Zilla of Zuron
|
|
I am happy to announce the new major release of Database .NET 19.8.
It is an innovative, powerful and intuitive multiple database management tool,
With it you can browse/grant objects, design tables, edit rows, run queries, generate scripts,
analyze/monitor SQL and import/export/migrate/sync data with a consistent interface.
Free, All-In-One, Portable, Single executable file and Multi-language.
Major New features from version 19.0 to 19.8:
- PostgreSQL 9.6+ compatibility
- Added Grant Manager for PostgreSQL (Pro)
- Added managing user permissions for PostgreSQL
- Added error detail message for PostgreSQL
- Added support for PostgreSQL arrays
- Added support for PostgreSQL 8.4~9.6 backup and restore (Req. Database .NET Additional Files)
- Added batch replacing cell values
- Ability to specify the location of SQL files
- Ability to add custom delimited file extensions
- Improved AutoComplete and IntelliSense
- Improved Selected Text to Query Builder
- Improved Generating Scripts
- Improved SQL History
- Improved Data Import and Data Export
- Improved Data Editor and Data Browser
- Improved Database Migration and Data Synchronization (Pro)
- ...and more
|
|
Full View / NID: 61867 / Submitted by: The Zilla of Zuron
|
|
PostgresDAC is a direct access component suite for RAD Studio and PostgreSQL
New milestone PostgresDAC release is out! Now with PostgreSQL 9.6 and Android target platform support.
From now and on NUMERIC fields are mapped to TFmtBcdField, that allows manipulating this type of values with immense flexibility.
This release contains breakdown change, thus developers should check their sources where NUMERIC fields are used.
Full changelog:
- [!] Android target platform support added
- [!] v9.6.0 client libraries added
- [!] v9.6.0 dump & restore libraries (pg_dump.dll, pg_restore.dll) added
- [!] NUMERIC fields are mapped to TFmtBcdField from now
- [+] TPSQLRestore.SchemaNames property introduced to specify multiple schemas
- [+] doStrictNames option added to TPSQLDump.Options
- [+] roStrictNames option added to TPSQLRestore.Options
- [*] TPSQLRestore.TableNames property to match all types of relations, not only plain tables
- [*] In TPSQLDump locally-made changes in privilege assignments for system objects
- [*] TPSQLRestore.SchemaName property removed as deprecated, use SchemaNames instead
- [-] Assigning MEMO fields to empty string may cause memory leak
Download
You're welcome to download the PostgresDAC v3.2.0 right now at:
http://microolap.com/products/connectivity/postgresdac/download/ or login to your private area on our site at
http://microolap.com/my/downloads/
Feedback
Please don't hesitate to ask any questions or report bugs with our Support Ticketing system available at
http://www.microolap.com/support/
|
|
Full View / NID: 61801 / Submitted by: The Zilla of Zuron
|
|
2ndQuadrant is proud to announce the release of repmgr version 3.2 which includes new features for Barman, replication cluster managing, standby cloning improvements, better integration of OS-level server commands, and other minor commands and improvements.
This release leverages improvements included with PostgreSQL 9.6 to provide support for switchover, a common administrative task where the roles of primary and standby server are swapped in a controlled manner to facilitate software and hardware maintenance.??
Note: repmgr 3.2 supports PostgreSQL 9.3 and later only.
What is repmgr?
repmgr is an open source package which greatly simplifies the process of setting up and managing replication using streaming replication within a cluster of PostgreSQL servers. Taking advantage of features introduced in PostgreSQL releases since 9.3, repmgr builds on PostgreSQL's core functionality to provide a smooth, user-friendly way of working with the complexities of replication and failover management in high-availability environments.
New features in repmgr 3.2
Barman Support
repmgr 3.2 provides enhanced integration with 2ndQuadrant's Barman backup and recovery manager. In particular, it is now possible to clone a standby from a Barman archive, rather than directly from a running database server. This means the server is not subjected to the I/O load caused by a backup, and there's no need to manage WAL retention on the database server. The standby can also use the Barman archive as a fallback source of WAL in case streaming replication is interrupted.??
Replication Cluster Monitoring
Usually, when working with more complex replication clusters spread over multiple locations, gaining an overview of connection status between nodes can be a tedious and time-consuming process. repmgr 3.2 provides two new commands which help with this, expanding the existing “repmgr cluster show”. You can read in depth about these commands in the README file.
Standby Cloning Improvements
In addition to the ability to clone directly from a Barman archive, various other improvements have been made to the standby cloning process. In particular, by default password-less SSH connection between servers is now optional and only needs to be provided for specific features.
Better Integration of OS Level Server Commands
By default, repmgr.conf will use PostgreSQL's standard pg_ctl utility to control a running PostgreSQL server. However, it may be better to use the operating system's service management system. To specify which service control commands are used, the following repmgr.conf configuration settings are available:?
- service_start_command
- service_stop_command
- service_restart_command
- service_reload_command
- service_promote_command
Read the formal release notes for information on other new commands, options, and improvements included in this release as well as upgrade instructions.
2ndQuadrant provides professional support services for repmgr — for more information, visit https://2ndquadrant.com/en/support/support-postgresql/.
|
|
Full View / NID: 61627 / Submitted by: The Zilla of Zuron
|
|
2ndQuadrant is proud to announce the release of pglogical 1.2 - now supporting PostgreSQL 9.6. Implemented entirely as a PostgreSQL extension, pglogical is a logical replication system that serves as a highly efficient method of replicating data as an alternative to physical replication.
In addition to a change in the way the output plugin and apply plugin are handled, some of the important feature updates and changes in this release include:
- keepalive tuned to much smaller values by default so that pglogical will notice network issues earlier
- Better compatibility when upgrading from PostgreSQL 9.4 - it's now safe to use the internal schema synchronization for that
- Improved conflict handling
- Improved support for replica triggers
- Several issues with initial synchronizations fixed
- Easier monitoring of the initial synchronization in pg_stat_replication
There are also several documentation improvements.
To find more information, including installation instructions, please visit the pglogical home page on the 2ndQuadrant website: https://2ndquadrant.com/en/resources/pglogical/
|
|
Full View / NID: 61594 / Submitted by: The Zilla of Zuron
|
|
PostgreSQL's repository for Debian and Ubuntu packages, apt.postgresql.org, has been extended to provide pre-built binary packages for a third architecture. ppc64el, the little-endian incarnation of IBM's POWER architecture, is joining the existing amd64 (64-bit x86 Intel) and i386 (32-bit x86 Intel) architectures.
The PostgreSQL 9.6 release is already included in the repository.
Just as on the existing architectures, all packages will be supported for all PostgreSQL major releases - which is currently all releases from 9.1 to 9.6. With only a few exceptions, all packages previously included in the repository have been compiled for ppc64el. [1]
Supported Debian distributions are Debian 8 (Jessie) and unstable (Sid); supported Ubuntu releases are 14.04 (Trusty) and 16.04 (Xenial).
This initiative has been led by 2ndQuadrant in cooperation with IBM Italy. Thanks must also be given to credativ for helping with the setup of the build infrastructure for the ppc64el architecture.
The ppc64el build host is provided by IBM Power Systems Linux Center - Montpellier.
Kind Regards,
Marco / Debian PostgreSQL Maintainers
[1] pg-partman is not available for 9.6 yet; psqlodbc and libpqtypes are not available on Trusty.
|
|
Full View / NID: 61520 / Submitted by: The Zilla of Zuron
|
|
The pgAdmin Development Team are pleased to announce the release of pgAdmin 4 version 1.0.
pgAdmin is the leading Open Source management and administration tool for PostgreSQL.
pgAdmin 4 is a complete rewrite of pgAdmin, built using Python and Javascript/jQuery. A desktop runtime written in C++ with Qt allows it to run standalone for individual users, or the web application code may be deployed directly on a webserver for use by one or more users through their web browser. The software has the look and feel of a desktop application whatever the runtime environment, and vastly improves on pgAdmin III with updated user interface elements, multi-user/web deployment options, dashboards and a more modern design.
The application was designed as a pluggable framework that can easily be extended with plugin modules to provide additional functionality to support other software in the PostgreSQL ecosystem, or functionality of forks of PostgreSQL.
For more information, screenshots, documentation and downloads, please see the website at:
https://www.pgadmin.org/
pgAdmin 4 is also bundled in the PostgreSQL 9.6 installers from EDB at:
http://www.enterprisedb.com/products-services-training/pgdownload
I'd like to take this opportunity to thank all those involved in the design, implementation, testing and documentation of pgAdmin 4, estimated at well over 10,000 hours of effort over the last year. For more information about the project, please see the blog post at:
http://pgsnake.blogspot.co.uk/2016/04/pgadmin-4-elephant-nears-finish-line.html
Finally, I'd like to thank the management at EDB for supporting this project and allowing me to enlist the efforts of over 15 employees from multiple teams. Without their support pgAdmin 4 would not exist today.
Dave Page,
pgAdmin Project Lead
|
|
Full View / NID: 61521 / Submitted by: The Zilla of Zuron
|
|
PostgreSQL 9.6, the latest version of the world's leading open source database, was released today by the PostgreSQL Global Development Group. This release will allow users to both scale up and scale out high performance database workloads. New features include parallel query, synchronous replication improvements, phrase search, and improvements to performance and usability, as well as many more features.
Scale Up with Parallel Query
Version 9.6 adds support for parallelizing some query operations, enabling utilization of several or all of the cores on a server to return query results faster. This release includes parallel sequential (table) scan, aggregation, and joins. Depending on details and available cores, parallelism can speed up big data queries by as much as 32 times faster.
"I migrated our entire genomics data platform - all 25 billion legacy MySQL rows of it - to a single Postgres database, leveraging the row compression abilities of the JSONB datatype, and the excellent GIN, BRIN, and B-tree indexing modes. Now with version 9.6, I expect to harness the parallel query functionality to allow even greater scalability for queries against our rather large tables," said Mike Sofen, Chief Database Architect, Synthetic Genomics.
Scale Out with Synchronous Replication and postgres_fdw
Two new options have been added to PostgreSQL's synchronous replication feature which allow it to be used to maintain consistent reads across database clusters. First, it now allows configuring groups of synchronous replicas. Second, the "remote_apply" mode creates a more consistent view of data across multiple nodes. These features support using built-in replication to maintain a set of "identical" nodes for load-balancing read workloads.
The PostgreSQL-to-PostgreSQL data federation driver, postgres_fdw, has new capabilities to execute work on remote servers. By "pushing down" sorts, joins, and batch data updates, users can distribute workload across multiple PostgreSQL servers. These features should soon be added to other FDW drivers.
"With the capabilities of remote JOIN, UPDATE and DELETE, Foreign Data Wrappers are now a complete solution for sharing data between other databases and PostgreSQL. For example, PostgreSQL can be used to handle data input going to two or more different kinds of databases," said Julyanto Sutandang, Director of Business Solutions at Equnix.
Better Text Search with Phrases
PostgreSQL's full text search feature now supports "phrase search." This lets users search for exact phrases, or for words within a specified proximity to each other, using fast GIN indexes. Combined with new features for fine-tuning text search options, PostgreSQL is the superior option for "hybrid search" which puts together relational, JSON, and full text searching.
Smoother, Faster, and Easier to Use
Thanks to feedback and testing by PostgreSQL users with high-volume production databases, the project has been able to improve many aspects of performance and usability in this release. Replication, aggregation, indexing, sorting, and stored procedures have all been made more efficient, and PostgreSQL now makes better use of resources with recent Linux kernels. Administration overhead for large tables and complex workloads was also reduced, especially through improvements to VACUUM.
Other Features
Version 9.6 has many other features added over the last year of development, among them:
- New system views and functions: pg_stat_wal_receiver, pg_visibility,
pg_config, pg_blocking_pids, pg_notification_queue_usage
- Command progress reporting support
- Cascade support for installing extensions
- pg_basebackup concurrency and replication slot support
- Wait Event support
- View editing and crosstabs in psql
- User-defined expiration for old snapshots
- Index-only scans for partial indexes
Additionally, the project has changed and improved the API for binary hot backups. As such, developers of custom backup software for PostgreSQL should do additional testing around the new version. See the Release Notes for more detail.
Links
|
|
Full View / NID: 61498 / Submitted by: The Zilla of Zuron
|
|
Barman (Backup and Recovery Manager) is an open-source administration tool for disaster recovery of PostgreSQL servers written in Python. Barman enables the remote online hot backup of multiple servers in business critical environments, helping make a DBA's life easier during the recovery stage - now with zero data loss.
What's New
The major release of version 2.0 is an important milestone in Barman's journey as it introduces support for a “streaming only” backup of a PostgreSQL server, removing the need for SSH connections altogether.
This is made possible by two significant improvements related to streaming replication:
- Transparent integration with pg_basebackup for backup operations
- Full support of replication slots for WAL streaming
Through streaming-only backups, Barman is now able to reach Docker and Windows users of PostgreSQL. From an architectural point of view, Barman is now able to offer even more versatility and flexibility by combining traditional SSH communications with PostgreSQL’s native streaming connections.
Another important addition is support for synchronous WAL streaming that allows zero data loss backups and reduces implementation costs of PostgreSQL clusters with “RPO=0” business continuity requirements.
Barman 2.0 also supports the new concurrent backup API introduced in PostgreSQL 9.6, eliminating the need for the pgespresso extension when taking backups from a standby server.
The new 'barman-cli' package improves integration of Barman with repmgr for better high availability outcomes.
Disaster Recovery
Recovery planning is frequently overlooked during business continuity planning, but failure is always an option. Unfortunately, our experience has shown us that typically, disaster recovery plans are only implemented after suffering severe data loss or down-time. Business critical environments must be prepared for the unexpected and Barman is the right tool organisations can use to be prepared.
Now, through synchronous WAL streaming, Barman allows a Recovery Point Objective (RPO) of 0. Barman now also supports PostgreSQL on Windows (experimental) and Docker. Improved support of very large databases and clusters is currently being developed for a future Barman release.
Professional Support for Barman
In addition to the disaster recovery and business continuity support already available through 2ndQuadrant, as the developers of Barman, the team at 2ndQuadrant provides superior support for Barman users. The turnkey disaster recovery solution service includes architecture analysis, installation, training and a final simulation with internal personnel. 2ndQuadrant offers custom solutions, development of new features, training, and 24/7 production support.
Upgrading from Barman 1.X
The 2.0 release requires that users explicitly configure their archiving strategy. Before, the file based archiver controlled by the ‘archiver’ option was enabled by default. When you upgrade your Barman installation to 2.0, make sure you add the appropriate line globally or for any server that requires it. Barman using officially distributed RPM and Debian packages will be automatically updated.
For installation or upgrade instructions, please see the "Links" section below.
For the comprehensive release notes, please read "Barman 2.0 Release Notes".
If you have any questions about Barman and disaster recovery scenarios using Barman, you can reach the dev team using the community mailing list.
To submit private inquiries regarding implementation, customised features or sponsorship opportunities email the team directly at info@pgbarman.org.
Links
|
|
Full View / NID: 61458 / Submitted by: The Zilla of Zuron
|
|
I am happy to announce the new major release of dbMigration .NET 3.7.
It 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, Access, dBase, FoxPro, Text, Excel, ODBC, OleDB...etc.
Free, All-In-One, Portable, and Single executable file.
Major New features from version 3.2 to 3.7:
- PostgreSQL 9.6+ compatibility
- Added Migrating VIEWS/FUNCTIONS/SEQUENCES definitions (PG->PG)
- Added Test mode (Only Top 100 Rows)
- Massive performance improvements
- Improved Automatic Mapping Types
- Improved Data Synchronization
- Improved Command-Line
- ...and more
The new version is immediately available for download.
|
|
Full View / NID: 61459 / Submitted by: The Zilla of Zuron
|
|
Starting today, you can take advantage of several new enhancements to Amazon RDS for PostgreSQL. These include new minor versions (9.3.14, 9.4.9 and 9.5.2), support for logical replication, event triggers, and the ability to use RDS for PostgreSQL as a source for AWS Database Migration Service.
New Minor Versions:
Customers can now launch new and upgrade their existing Amazon RDS for PostgreSQL instances to new PostgreSQL minor versions 9.3.14, 9.4.9, and 9.5.4, using either the AWS console or Amazon RDS API. These new minor version releases contain several enhancements and fixes to PostgreSQL. To learn more about these new versions, please refer to their release notes:
• Release Notes for 9.3.14
• Release Notes for 9.4.9
• Release Notes for 9.5.4
Logical Replication and support for AWS Database Migration Services
Amazon RDS for PostgreSQL now supports logical replication on RDS for PostgreSQL versions 9.4.9 and 9.5.4. With logical replication, we have added support for logical decoding, and you can setup logical replication slots on your instance and stream changes from the database through these slots. A new rds_replication role, assigned to the master user by default, can be used to grant permissions to manipulate and stream data through logical slots. To enable logical replication, set the parameter rds.logical_replication to 1. These logical slots also enable the RDS for PostgreSQL to be used as a source for AWS Database Migration Service (DMS). You can learn more about using RDS for PostgreSQL as a source for DMS in the AWS Database Blog and RDS documentation.
Event Triggers:
Amazon RDS now supports the event triggers in PostgreSQL versions 9.4.9 and later and version 9.5.4 and later. The master user account can be used to create, modify, rename, and delete event triggers. Event triggers are at the DB instance level, so they apply to all databases on an instance. For more information about event triggers for Amazon RDS for PostgreSQL, refer to the RDS documentation.
New Parameter for RAM Disk Size:
Amazon RDS for PostgreSQL now supports a new parameter, rds.pg_stat_ramdisk_size, which can be used to define the system memory allocated to a RAM disk for storing PostgreSQL stats_temp_directory. Under certain workloads, it can result in improved performance and decreased I/O requirements. You can read about the details of the new parameter here in the RDS documentation.
All the enhancements mentioned above are available in all regions. You can learn more about Amazon RDS for PostgreSQL on the RDS product page and the RDS documentation.
|
|
Full View / NID: 61393 / Submitted by: The Zilla of Zuron
|
|
SQL Maestro Group announces the release of PostgreSQL PHP Generator 16.9, a powerful GUI frontend for Windows that allows you to generate feature-rich CRUD web applications for your PostgreSQL database.
The new version is immediately available at
http://www.sqlmaestro.com/products/postgresql/phpgenerator/.
Most of software features can be seen in action in our Feature Demo and NBA Demo applications.
Top 20 new features:
- Column Filtering.
- Custom Form Layouts.
- Enhanced Master/Detail Views.
- Record comparison.
- Multi-Row Column Headers.
- Breadcrumb navigation.
- Automatic generation of index pages.
- On-the-Fly Adding New Items to Lookup Controls.
- Improved Filter Builder.
- Quick Edit.
- Adding multiple records from a single Insert form.
- Geo Charts.
- Permissions and RLS for all-level Details.
- Flexible card views.
- Enhanced JavaScript API.
- OnGetCustomExportOptions event.
- OnGetCustomUploadFileName event.
- Built-in Lightbox component for external images.
- Simple Data Grid Styling.
- A number of GUI improvements.
There are also some other useful things. Full press release is available at the SQL Maestro Group website.
|
|
Full View / NID: 61315 / Submitted by: The Zilla of Zuron
|
|
Full View / NID: 61314 / Submitted by: The Zilla of Zuron
|
|
I am happy to announce the release of PGLiveBackup (Beta 1). PGLiveBackup is a complete backup and restore automation solution written 100% using BASH only - which makes it fully "plug and play" deployable accross linux/unix distros. Plus, the metadata repository is managed as a schema in the local postgres database.
Please read the documentation for more information.
http://www.pglivebackup.org
|
|
Full View / NID: 61316 / Submitted by: The Zilla of Zuron
|
|
Helsinki, Finland — September 15, 2016 — Aiven brings easy, powerful hosted PostgreSQL to Microsoft Azure
Aiven
adds service availability for nineteen new cloud regions from the Microsoft Azure cloud, making Aiven the cloud database provider with the widest geographic availability in the world. Microsoft Azure is a leading global cloud provider and what makes them special is their high number of data centers around the world, currently totaling 30+ regions.
Aiven PostgreSQL is an easy-to-use Database-as-a-Service (DBaaS) offering providing Highly Available service plans with advanced features. Aiven PostgreSQL backups are automatic and zero-downtime database plan upgrades allow easy upgrades from single-node starter plans to a geo-replicated premium setups. Database services can even be migrated between different cloud providers with no downtime. Aiven PostgreSQL plans include all of the most popular PostgreSQL extensions such as PLv8 and PostGIS. All Aiven services keep your data safe and encrypted at all times, both in transit and at rest.
The first batch of new Azure cloud regions that are immediately available are all from North America and Europe. Asian and South American regions will be made available in the upcoming weeks.
The new Aiven Azure regions that are immediately available:
- United States: Iowa (Central US), Virginia (East US), Virginia (East US 2), Illinois (North Central US), Texas (South Central US), California (West US), Washington (West US 2), Wyoming (West Central US)
- Europe: Ireland (North Europe), Netherlands (West Europe), England (UK South), Wales (UK West)
- Canada: Ontario (Canada Central), Quebec (Canada East)
The following regions will become available in the upcoming weeks:
- South America: Brazil (Brazil South)
- Asia: Hong Kong (East Asia), Singapore (Southeast Asia), Japan (Japan East), Japan (Japan West)
New services can be launched in the new Azure regions today and using Aiven's zero-downtime migration, it is also possible to easily migrate your existing services to Microsoft Azure.
About Aiven
Aiven is a Finnish, Helsinki-based cloud technology startup company focusing on delivering easy to use, yet technically advanced cloud database services to companies around the world. Aiven offers hosted PostgreSQL, Elasticsearch, Apache Kafka, Redis and InfluxDB services on five different cloud providers: Amazon Web Services, Google Cloud, DigitalOcean, UpCloud and Microsoft Azure.
https://aiven.io/
https://aiven.io/postgresql
|
|
Full View / NID: 61294 / Submitted by: The Zilla of Zuron
|
|
|
.....
|
|