
How to Remove Orphan Large Objects in PostgreSQL
To manage Binary Large Objects (BLOBS) in PostgreSQL, use the lo_unlink() function to remove them properly. Failing to do so can leave orphaned records, but vacuumlo can help clean them up.

To manage Binary Large Objects (BLOBS) in PostgreSQL, use the lo_unlink() function to remove them properly. Failing to do so can leave orphaned records, but vacuumlo can help clean them up.

The “RockYou2024” password leak contains 9,948,575,739 unique plaintext passwords, making it valuable for cybercriminals aiming to perform brute-force attacks. Ensuring the security of Oracle databases is crucial, as weak passwords pose a significant vulnerability. To mitigate this risk, it is recommended to compare database passwords against the 1 million most common ones. A provided SQL script guides this process and demonstrates how to perform the comparison.

PostgreSQL’s pg_amcheck is an essential tool for ensuring data integrity. Like Sherlock Holmes, it diligently detects anomalies, offering early detection of data corruption from hardware failures, software bugs, or system crashes. This tool, though not glamorous, is vital for proactive maintenance. Administrators can use pg_amcheck to identify issues.

After updating to release 19.22, issues arose with Flashback Data Archive (FDA). Despite bug fixes(35957640), internal indexes were created with the DEFAULT PARALLEL degree. Additionally, split operations caused related indexes to become unusable. A debug of the FBDA process revealed that the split operations lack an “UPDATE INDEXES” clause and no index rebuild operation is done internally. The test case provided highlights the issues. These concerns have been raised in a Service Request for resolution.

PostgreSQL allows most DDL commands to be rolled back within a transaction block, unlike in many commercial database systems where DDL commands automatically commit the current transaction. With exceptions like DROP DATABASE and CREATE/DROP TABLESPACE, PostgreSQL ensures that all DDL operations are transactional, allowing for rollback as needed.

This blog introduces the concept of holistic patching for Oracle Enterprise Manager, which simplifies and consolidates patch management for its various components. The method aims to reduce complexity and downtime by bundling updates into a single package, allowing organizations to focus on core activities. The process involves updating the OMSPatcher and executing a simple command for patching, significantly streamlining the patching process for Enterprise Manager.