Experts in Postgres and Open Source Infrastructure

Command Prompt is pleased to announce PgManage version 1.0b. This release adds two major features, 3 major bug fixes and over a dozen changes and improvements. PgManage is a Postgres centered multi-database management Open Source project.

New features:

• Added backup/restore support for PostgreSQL
• First version of PgManage Handbook was published to https://pgmanage.readthedocs.io/en/latest
  

Major Bugs fixed:

• Fixed .AppImage compatibility issues for newer Linux distributions which do not have libcrypt installed
• Added …

To be truly successful in life, we must have an equilibrium. We must balance desire, learning from success and failure, fear, exhaustion, passion, employer satisfaction, relationships, children, personal ambition and growth, tee-ball games, disappointment, ballet classes, illness, client management, and unexpected events. How can we manage all of these tasks when we try to put everything into two separate boxes? We can’t and that is why people get burned out.

PgManage is a Postgres centered multi-database management Open Source project. It is a fork of the previously well received project OmniDB that had been abandoned. Command Prompt has taken the helm of this project to ensure a quality project focused on the Management of PostgreSQL and related technologies.

• Source: https://github.com/commandprompt/pgmanage
• Website and Binaries: https://commandprompt.com/products/pgmanage/
• Full Documentation: https://pgmanage.readthedocs.io/en/latest/
• Community: https://discord.gg/FvweAhhUeu
  
  

Major Changes from OmniDB

New features:

• new connection management UI
• added …

Life is about people

Databases are a vital component of any application or website, especially with the reliance on data to meet our end users’ needs. PostgreSQL databases are robust and limitless in their capabilities but not when they’re operating like it’s 1999.

Do you have any outdated end-of-life (EOL) PostgreSQL instances?

EOL software is especially prone to bugs and security issues, but scheduling and performing critical updates and upgrades can be challenging. The …

Recently I have been working on PostgreSQL benchmarks for its data checksums feature. This incredibly valuable option to initdb -- introduced in version 9.3 in 2013 -- allows quick detection of corrupted disk data pages. It provides the glorious opportunity to simply failover to a standby before your data becomes corrupted, rather than endure the horror of discovering the corruption afterward and attempting to recover.

But people care as much …

The fifth and last in a series of blogs covering common mistakes in Database and Application designs for financial calculations.

Method of Rounding:

There are many methods of rounding

1. Half Round Up
2. Half Round Down
3. Round Towards Zero
4. Round Away from Zero
5. Round Half To Even
6. Round Half To Odd
7. Random Round

The built-in method of rounding in PostgreSQL is Half Round Up. Unfortunately, it is not the best approach, …

The fourth in a series of blogs covering common mistakes in Database and Application designs for financial calculations.

Database Driver, or Application Framework Created Error:

The database driver or application framework created errors are probably the hardest to find, as we are the consumer not the writer of the tool, with many assuming the casting is correct. However, we must review the documentation or the library’s code to know how …

The third in a series of blogs covering common mistakes in Database and Application designs for financial calculations.

Order of Operations and Storing Aggregate Results:

When working with float data types, order of operations will affect the ending value.

Consider 3:

Python3:

justin@Debian10:~$ python3

Python 3.7.3 (default, Jul 25 2020, 13:03:44) 

>>> (1234.567 * 3.333333) + (1.234567 * 3.333333)

4119.338,144,732,812

>>> (1234.567 + 1.234567 ) * 3.333333 …

The second in a series of blogs covering common mistakes in Database and Application designs for financial calculations.

Inconsistent precision scaling:

This is probably the most common mistake in database design that I observe. It is understood to use exact data types (such as numeric) and the precision must be fixed, but for whatever reason the decision is made that it’s OK for one table to use numeric(12,4),a second table …