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.

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.

Dans la continuité de VMworld 2016 Europe, nous ferons un …

Read More

A day doesn&#rsquo;t go by when we don&#rsquo;t read an article about how businesses are incorporating digital as a core component for strategic transformation. The most amusing story I&#rsquo;ve heard recently that illustrates this digital business transformation is Domino&#rsquo;s. I&#rsquo;m sure you—like millions of others—have seen the below commercial and even ordered a large two […]

The post The Domino&#rsquo;s Effect: Why Innovation Begins by Taking a Wrecking Ball to IT Silos appeared first on VMware End-User Computing Blog.

Today is one of my favorite release days! We are releasing the remainder of our Horizon and Challenge labs for the 2017 Hands-on Labs catalog. There is some great new content we are releasing in the Mobility catalog for Horizon. These labs focus on Identity Manager and application management and delivery with App Volumes and […]

The post New Horizon and Challenge Labs Released! appeared first on VMware Hands-On Lab (HOL) Blog.

You can’t miss this - VMware vForum Online is happening on November 3rd! Join our experts at this free, online event to learn more about the cloud, virtualization, and business mobility. At this virtual event, you&#rsquo;ll discover how vCloud Air can seamlessly extend private workloads to the cloud while securely consolidating infrastructure and resources. Sign […]

The post Join Our VMware vCloud Air Sessions at vForum Online November 3rd! appeared first on VMware vCloud Blog.

For while now, there&#rsquo;s been some speculation that VMware vCloud Directorwas no longer a priority for VMware – but that couldn&#rsquo;t be further from the truth. With the release of vCloud Director 8.10 this spring, VMware has doubled down on its dedication to enhancing the product, and we&#rsquo;ve even expanded our training program to keep […]

The post MythBusters: Debunking Three Common Myths Around vCloud Director appeared first on VMware vCloud Blog.

  By Jean Oliveira Thanks for taking the time to read my previous blog post?Certificates for Dummies?where I walked through the process of enabling PSC as a VMware Certificate Authority (VMCA). In this blog post I will demonstrate the process for replacing vCenter Server Certificates with those issued by VMCA. First, I strongly recommend that […]

The post Certificates for Dummies – Part Two: Replacing vCenter Server Certificates with VMware Certificate Authority appeared first on VMware TAM Blog.

As VMware continuously transforms offerings to extend customer success, we want our partners to grow with us. So, if you&#rsquo;re a VMware Professional Partner reading this, we&#rsquo;re happy to say you&#rsquo;re one step closer to multiplying your deal size. You might be asking yourself, &#rsquo;Is that for real?&#rdquo; The answer: yes. An average 4x increase […]

The post Dispelling Partner Journey Myths: How to Move from Professional to Enterprise appeared first on Power of Partnership.

Reading a food label. Navigating a crosswalk. Recognizing a friend. These tasks are easy for most people, but can be difficult for those who are visually impaired. To bring more independence to the lives of people with limited sight, a new wearable device called Horus uses GPU-powered deep learning and computer vision to help them […]

The post This Powerful Wearable Is a Life-Changer for the Blind appeared first on The Official NVIDIA Blog.

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:

• Download
• Release Notes
• Security Page
• Versioning Policy

The U.S. needs to invest more in AI research, leading policymakers told a sellout crowd of about 1,000 attendees at NVIDIA’s inaugural GPU Technology Conference in Washington D.C.. Speaking during the opening keynotes, Jason Furman, chairman of the White House Counsel of Economic Advisers, and France Córdova, director of the National Science Foundation, said that […]

The post Top DC Policymakers Say They Worry U.S. Not Investing Enough in AI appeared first on The Official NVIDIA Blog.