migrations Archives

Tech Optimizer

May 15, 2026

From commit to cloud: Powering what’s next for PostgreSQL

PostgreSQL is widely used across various industries, supported by Microsoft through significant investments, including 345 commits to the latest release and a dedicated team of contributors. It is recognized for its ability to handle complex production challenges, such as transactional integrity and concurrency management. Microsoft operates PostgreSQL globally, informing upstream contributions based on real-world deployment experiences. The database is increasingly integrated into AI applications, with Azure Database for PostgreSQL and Azure HorizonDB focusing on AI functionalities. Microsoft offers multiple deployment models to accommodate different workload needs, including Azure Database for PostgreSQL for open-source workloads and Azure HorizonDB for cloud-native systems. Recent contributions from Microsoft include enhancements in asynchronous I/O, vacuum behavior, and query planning. Azure HorizonDB is designed for high-throughput, low-latency systems requiring horizontal scaling. Microsoft also invests in developer tools, such as a Visual Studio Code extension for PostgreSQL, and sponsors PostgreSQL conferences and user groups globally.

AppWizard

May 12, 2026

Android Apps on Windows 11: Safe Alternatives After WSA

In 2025, Microsoft announced it would discontinue support for the Windows Subsystem for Android (WSA), making Android applications non-functional on Windows 11. This decision surprised many users in Indonesia who relied on these applications. HP developed a guide outlining secure alternatives to WSA, which included reputable Android emulators like BlueStacks, LDPlayer, and NoxPlayer, as well as native Windows alternatives such as Microsoft Teams and Microsoft 365 apps. Users were advised against unverified APK sideloading, unofficial emulators, and modified apps due to security risks. Microsoft’s end of support means no further security updates or bug fixes will be provided, and integration with the Amazon Appstore will cease. Users can continue using WSA apps, but they will be exposed to potential security threats. To migrate data from WSA, users were instructed to inventory apps, research alternatives, and export app data before performing a clean uninstall. Best practices for running Android apps safely on Windows included downloading from official sources and keeping software updated.

Tech Optimizer

May 1, 2026

Ghost: A Database for Our Times?

Ghost, developed by ghost.build, is an "agent-first" Postgres database platform designed for AI-related applications, allowing developers and AI agents to create, fork, inspect, query, manipulate, and delete databases easily. It is free to use and hosted on Ghost’s Cloud infrastructure, making it suitable for testing, prototyping, and disposable database environments. Users can create databases on demand, execute SQL queries, and discard them when finished, contrasting with traditional managed databases. Ghost integrates with AI tools like Codex and Claude Code, providing direct database management capabilities through its MCP server. To install Ghost, users need a supported coding agent and a GitHub account. Installation commands differ for Linux, macOS, and Windows. After installation, users can verify the Ghost MCP server and interact with it through their coding agents. Examples of using Ghost include creating a sales data database, utilizing Ghost CLI commands, and experimenting with databases through AI agents. Ghost allows for rapid database manipulation and is ideal for proofs of concept and experimentation, although caution is advised before using it for production data.

Tech Optimizer

May 1, 2026

Backstage Ditches Postgres for Databricks Lakebase

The divide between operational and analytical databases is diminishing, as evidenced by Databricks integrating Spotify's Backstage with its Lakebase, transitioning from PostgreSQL to a unified data platform. Lakebase now offers a serverless PostgreSQL interface within Databricks, allowing Backstage to operate without awareness of the underlying changes. The integration involved updating configurations and addressing authentication challenges using OAuth JWTs. The integration transforms the database development lifecycle by enabling near-instant database branching through Lakebase's copy-on-write architecture, allowing developers to focus on testing changes rather than safety. Branching creates a pointer to existing data, making the operation instantaneous. Point-in-Time Recovery (PITR) allows for quick restoration of data, demonstrated by a recovery process that took less than four seconds. The goal is to integrate database branching into developer workflows seamlessly, making it automatic. This change could enhance developer productivity by allowing live data testing from the start, eliminating the need for mock objects, and resolving common issues related to staging environments. The traditional constraints of slow and costly database copies will become obsolete, prompting teams to reconsider how much time they spend on workarounds for now-nonexistent constraints.

Tech Optimizer

April 25, 2026

Telangana Migrates MeeSeva to Open-Source PostgreSQL, Cuts ₹10 Crore Annual Cost

The Telangana government has transitioned its MeeSeva platform from Oracle to the open-source PostgreSQL database, announced by Ravikiran Tirumala, Commissioner of Electronic Services Delivery. MeeSeva processes over 80,000 government-to-citizen transactions daily, totaling nearly 20 crore transactions since its inception. The migration, using the open-source tool “ora2pg,” took less than four hours of downtime. The annual cost of Oracle licensing and maintenance was around ₹10 crore, while the migration cost was under ₹1 crore, leading to estimated recurring annual savings of about ₹10 crore. PostgreSQL has effectively managed high transaction volumes without performance issues. Telangana plans to document and share its migration process to encourage the adoption of open-source technologies in other government systems.

Winsage

April 19, 2026

Zorin OS 18.1 adds guided migrations, stronger app compatibility and wider hardware support, making switching from Windows far more practical for millions [clone]

Zorin OS has released version 18.1, enhancing hardware compatibility and introducing fingerprint reader support for older devices. The update recommends native Linux alternatives when detecting Windows applications, making it easier for users transitioning from Windows. Since the end of support for Windows 10, Zorin OS has gained popularity, reaching 3.3 million downloads. The update supports over 240 Windows applications, suggesting compatible Linux versions, and includes improvements to desktop features and pre-installed applications. Zorin Lite has also been updated to version 17.3 with fingerprint reader support and a redesigned File Manager. Meanwhile, Windows 11 is facing challenges in adoption due to hardware requirements and design issues, prompting discussions about the potential need for Windows 12. Alternative operating systems like Zorin OS are becoming more appealing to users dissatisfied with Windows.

Tech Optimizer

April 17, 2026

Why Postgres wants NVMe on the hot path, and S3 everywhere else

Efforts to merge storage roles into a single solution are ongoing, particularly with Amazon S3's durability and cost-effectiveness. In PostgreSQL, achieving a durable commit requires flushing the Write-Ahead Log (WAL) before signaling transaction completion, which can take tens of microseconds on high-performance NVMe drives but extend to milliseconds on slower storage. This latency impacts Online Transaction Processing (OLTP) systems and user response times. Benchmark studies show that systems with faster local storage outperform those with slower alternatives as workloads exceed memory capacity. The fsync operation in PostgreSQL is a commitment rather than a simple write, with enterprise-grade SSDs performing better due to power-loss protection. Read operations also face challenges, as PostgreSQL's need for small, latency-sensitive reads conflicts with S3's design for larger, higher-latency requests. As the working set exceeds memory, storage latency becomes a critical performance factor. Modern managed PostgreSQL systems typically do not place object storage in the critical commit path, instead maintaining a fast log or cache close to the database while relegating colder data to remote storage. Recent PostgreSQL developments, such as asynchronous I/O support in version 18, aim to leverage fast storage more effectively. S3 is valuable for tasks like WAL archiving and backups, but these should be kept separate from the commit path to avoid resource contention. The solution involves using both NVMe and S3, with fast storage managing commits and cache misses, while object storage handles archives and backups. PostgreSQL performs best when hot and cold storage functions are clearly delineated.

Tech Optimizer

April 15, 2026

Connecting .NET Lambda to Amazon Aurora PostgreSQL via RDS Proxy

Many organizations are modernizing legacy .NET applications while reducing database costs and enhancing scalability, particularly during migrations to AWS Lambda and transitions from SQL Server to Amazon Aurora PostgreSQL-Compatible Edition. The process involves connecting Lambda functions to Aurora PostgreSQL using Amazon RDS Proxy, with AWS Secrets Manager managing secure credential storage. The architecture includes a .NET Lambda function interfacing with Aurora PostgreSQL via RDS Proxy, which provides connection pooling to minimize database connection overhead. The solution requires a CloudFormation template to provision resources such as a VPC with private subnets, an Aurora PostgreSQL cluster, RDS Proxy, and Secrets Manager. The RDS Proxy is configured with parameters including PostgreSQL engine family, idle client connection timeout, and Secrets Manager secret. A Windows EC2 instance is provisioned, and access is facilitated through AWS Systems Manager Fleet Manager. The solution includes creating a sample table named "employee" in the database and a new .NET Lambda project that utilizes Npgsql for database connections. The Lambda function is deployed using the AWS CLI, and testing involves invoking the function and retrieving logs from Amazon CloudWatch. Finally, resources created during the process should be deleted to prevent ongoing charges.

Tech Optimizer

April 11, 2026

Google Cloud Highlights Ongoing Work on PostgreSQL Core Capabilities

Google Cloud has made technical contributions to PostgreSQL, focusing on advancements in logical replication, upgrade processes, and system stability. Key developments include the evolution of logical replication towards active-active configurations with automatic conflict detection to identify row-level conflicts during replication. This progress has sparked discussions about consistency models in database systems. Enhancements have also expanded logical replication to include sequences, reducing manual synchronization needs. Improvements to pg_upgrade have streamlined large object management and reduced upgrade times, while ensuring WAL data retention and schema constraint preservation. Bug fixes have addressed issues with index pages, extension loading, and WAL flush logic. Future features under development include a structured conflict log for replication and enhancements to parallel data export in pg_dump.

Tech Optimizer

April 11, 2026

Database Branching in Postgres: Git-Style Workflows with Databricks Lakebase

Database branching is a modern approach that addresses the limitations of traditional database management in development workflows. Unlike conventional database copies, which require significant time and resources to duplicate data and schema, database branching allows for the creation of isolated environments that share the same underlying storage. This method utilizes a copy-on-write mechanism, enabling branches to be created in seconds regardless of database size, with storage costs tied only to the changes made. Key features of database branching include: - Branch creation time: Seconds, constant regardless of database size. - Storage cost: Proportional to changes only, not the total data size. - Isolation: Each branch has its own Postgres connection string and compute endpoint. - Automatic scaling: Idle branches can scale compute to zero, incurring costs only when active. The architecture supporting this approach separates compute from storage, allowing multiple branches to reference the same data without conflict. This design facilitates time travel capabilities, enabling branches to be created from any point in the past for instant recovery and inspection. Database branching unlocks new workflows, such as: - One branch per developer, providing isolated environments for each engineer. - One branch per pull request, automating branch creation and deletion tied to PRs. - One branch per test run, provisioning fresh databases for each CI pipeline execution. - Instant recovery from any point in time within a designated restore window. - Ephemeral environments for AI agents, allowing programmatic database provisioning. Databricks Lakebase offers this database branching capability, transforming the database from a bottleneck into a streamlined component of the development process.