• PostgreSQL Database and Patroni Security

    Secure PostgreSQL: Database, Patroni, Etcd and Pgbackrest

    This guide provides a comprehensive approach to secure the PostgreSQL environment, including the database, Patroni, Etcd, and Pgbackrest. It covers key aspects such as authentication, encryption, auditing, parameter hardening, patch management, network security, and backup strategies along with securing Patroni REST APIs and Etcd’s SSL configuration. Additionally, it emphasizes the importance of securing PGBackrest endpoints with TLS encryption to protect sensitive data during backup processes, ensuring comprehensive security for the entire PostgreSQL database environment.


  • Speed up Spatial Operators - SPATIAL_VECTOR_ACCELERATION parameter

    “spatial_vector_acceleration” parameter  improves Oracle spatial vector query performance

    Oracle Database 12c and above introduce significant speed improvements for spatial operations. The SPATIAL_VECTOR_ACCELERATION parameter, set to TRUE, enhances index performance, geometry engine efficiency, and CPU and memory usage. Oracle Spatial and Graph is included in the Oracle Database license at no extra cost. Rebuilding spatial indexes with INDEXTYPE=MDSYS.SPATIAL_INDEX_V2 can simplify index management and improve performance for specific queries.


  • Offline Upgrade of PostgreSQL and Patroni

    How to Upgrade PostgreSQL, PostGIS and Patroni in Offline Environment

    This blog post outlines the process of upgrading a PostgreSQL environment with no internet, covering major and minor upgrades, as well as updates to various extensions. It details the specific steps for upgrading each component, including Patroni, pgbackrest, PostGIS, pg_cron, and Oracle_FDW. The post emphasizes the importance of careful planning and thorough testing for major upgrades, along with considerations for downtime and data replication. Additionally, it provides guidance on memory resource management and configuration adjustments during the upgrade process.


  • Oracle Database Patching using Ansible

    Oracle Database Patching by Using Ansible

    This post discusses using Ansible Playbooks to patch Oracle database software, from installing Ansible to completing the patching process. It provides detailed playbooks for creating new database software directories, applying release updates and one-off patches, running datapatch, and removing old database homes. The author also revised the playbooks for better readability and compatibility.


  • Using Ansible to patch Oracle Grid Infrastructure

    Oracle Grid Patching by using Ansible

    This blog post discusses the usage of Redhat Ansible to patch grid infrastructure, emphasizing its simplicity and efficiency. It explains the process of installing Ansible, preparing the environment, and executing playbooks for grid software patching with detailed steps. The author also provides valuable insights into the revision of playbooks for best practices.


  • No bind peeking when using TOAD

    TOAD and sqlplus have Different Execution Plans: Bind variable peeking

    The post discusses a performance issue where an identical query yields different execution plans in TOAD and sqlplus due to various factors such as statistics, physical differences, settings, and OCI commands. The issue is identified as related to Adaptive Cursor Sharing (ACS), and the difference in behavior is observed when running the query with different bind values. The response also mentions a change in TOAD’s OCI Array Buffers size option, resolving the issue in the upcoming beta release.