Skip to main content

Welcome to DBA Master – Database Tips, Tricks, and Tutorials

Welcome to DBA Master ! This blog is dedicated to all things related to database administration , SQL optimization , and performance tuning . Whether you're a beginner or a seasoned DBA, you'll find practical guides, troubleshooting tips, and real-world tutorials to help you work smarter with data. What to Expect: SQL performance tuning tips Indexing strategies Backup and recovery best practices High availability and replication techniques Database creation, configuration, and setup Monitoring queries and scripts for proactive performance management Migration guides across different database platforms Security essentials and best practices Recommended tools for DBAs Real-world error fixes and how to solve them Stay tuned — exciting content is coming soon. Feel free to bookmark and share: www.dbamaster.com ! Thanks for visiting!

PostgreSQL Physical Storage

base

Subdirectory containing per-database subdirectories.

global

Subdirectory containing cluster-wide tables, such as pg_database.

pg_commit_ts

Subdirectory containing transaction commit timestamp data.

pg_dynshmem

Subdirectory containing files used by the dynamic shared memory subsystem.

pg_logical

Subdirectory containing status data for logical decoding.

pg_multixact

Subdirectory containing multitransaction status data (used for shared row locks).

pg_notify

Subdirectory containing LISTEN/NOTIFY status data.

pg_replslot

Subdirectory containing replication slot data.

pg_serial

Subdirectory containing information about committed serializable transactions.

pg_snapshots

Subdirectory containing exported snapshots.

pg_stat

Subdirectory containing permanent files for the statistics subsystem.

pg_stat_tmp

Subdirectory containing temporary files for the statistics subsystem.

pg_subtrans

Subdirectory containing sub transaction status data.

pg_tblspc

Subdirectory containing symbolic links to tablespaces.

pg_twophase

Subdirectory containing state files for prepared transactions.

log or pg_log (before postgres 9.6)

File recording the log file(s) currently written to by the logging collector.

pg_wal or pg_xlog(before postgres 9.6)

Subdirectory containing WAL (Write Ahead Log) files.

pg_xact or pg_clog (before postgres 9.6)

Subdirectory containing transaction commit status data.

pg_hba.conf

A file containing client(hostname, dbname, username and password method)
authentication and authorization.

postgresql.conf

A file containing server parameters.

postgresql.auto.conf

A file used for storing configuration parameters that are set by ALTER SYSTEM.

postmaster.opts

A file recording the command-line options the server was last started with.

postmaster.pid

A lock file recording the current postmaster process ID (PID), cluster data directory path, postmaster start timestamp, port number, Unix-domain socket directory path (empty on Windows), first valid listen_address (IP address or *, or empty if not listening on TCP), and shared memory segment ID (this file is not present after server shutdown).

PG_VERSION

A file containing the major version number of PostgreSQL

Comments

Popular posts from this blog

Oracle Database 19C Performance Tunning - PART 1

Advantages: 1. Improved Query Performance •    Optimized SQL execution plans lead to faster query response times. •    Reduces unnecessary full table scans and improves indexing strategies. •    Parallel execution tuning speeds up large data processing tasks. 2. Better Resource Utilization •    Efficient use of CPU, memory, disk I/O, and network resources. •    Reduces contention on Redo Logs, Undo Tablespaces, and Buffer Cache. •    Helps in load balancing across multiple instances in RAC (Real Application Clusters). 3. Increased System Scalability •    Ensures that the database can handle a growing number of users and transactions. •    Proper tuning allows scaling without degrading performance. •    Optimized parallel processing ensures better performance on multi-core servers. 4. Lower Infrastructure Costs •    Reduces the need for add...

Oracle RMAN Backup And Restore

RMAN: (Oracle 8) RMAN (Recovery Manager) is a utility provided by Oracle Database to perform backup, restore, and recovery operations. It is a command line tool. Features of RMAN in Oracle 19c Comprehensive Backup Capabilities: Full and incremental backups. Block-level backups for efficient data storage. Archived redo log backups. Fast Recovery Area (FRA) integration for centralized backup storage. Efficient Recovery Options: Point-in-time recovery (PITR). Complete and incomplete recovery. Flashback database capabilities for quick undo of changes. Multitenant Database Support: RMAN fully supports container databases (CDBs) and pluggable databases (PDBs). Provides flexibility to back up and recover individual PDBs or entire CDBs. Automatic Space Management: Manages disk space in the FRA. Automatically deletes obsolete backups and archived logs. Data Deduplication and Compression: Backup optimization through block-level deduplication. Built-in compression algorithms to reduce storage req...

Oracle 19c Database Software Installation in OEL8

 Pre-requisites for OS level:            Set the static IP Address     Disable the Firewall (systemctl stop firewalld & systemctl disable firewalld)     set SELINUX=permissive on /etc/selinux/config  ##Need to restart the server use init 6 Oracle Installation Pre-requisites Methods     Automatic Setup     Manual Setup      Automatic requisites Setup: (avoid step 1 to step 5): dnf install -y oracle-database-preinstall-19c Install the dependencies: curl -o oracle-database-preinstall-19c-1.0-2.el8.x86_64.rpm https://yum.oracle.com/repo/OracleLinux/OL8/appstream/x86_64/getPackage/oracle-database-preinstall-19c-1.0-2.el8.x86_64.rpm dnf -y localinstall oracle-database-preinstall-19c-1.0-2.el8.x86_64.rpm Manual Setup: step 1: Add the karenl parameters and values vi /etc/sysctl.conf     fs.file-max = 6815744 kernel.sem = 250 32000 100 128 kernel....