PostgreSQL 18 Introduces Incremental Backup Support via pg_basebackup

·3 views

PostgreSQL 18 adds native incremental backup capability through the pg_basebackup utility, requiring WAL summarization to be enabled via the summarize_wal parameter in postgresql.conf. A full base backup is first created using pg_basebackup, which generates a backup_manifest file that serves as a reference point for subsequent incremental backups. Any database changes made after the full backup — such as new tables or inserted data — are captured exclusively in the incremental backup. The pg_combinebackup tool is then used to merge the full and incremental backups before restoring the database. This workflow significantly reduces storage and time costs compared to taking repeated full backups.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How Trueforge, OneCLI, and Lightdash Are Shaping Production-Ready AI Agents in 2026

By 2026, building production-grade AI agents has evolved into a rigorous architectural discipline, moving well beyond simple chatbot wrappers. A five-layer 'Agency Stack' has emerged, covering interface, orchestration, execution, data memory, and observability. Failures seen in 2024 and 2025, including hallucinated code and unmonitored token spend, were largely traced to weak execution and observability layers. Three companies, Trueforge, OneCLI, and Lightdash, offer key lessons across developer tooling, local-first CLI agents, and structured data analytics respectively. Their approaches highlight the importance of sandboxed execution, deterministic verification loops, and fine-grained tool permissions in deploying reliable AI agents at scale.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build API Docs That Actually Help Developers Succeed

Effective API documentation requires more than listing endpoints — it must guide developers through a first successful request, exact reference details, and clear error recovery. A well-structured quickstart should provide credentials, a complete sample request, an expected response, and links to next steps. Reference pages must precisely document parameters, types, defaults, constraints, and response schemas so developers can scan without guessing. Guides and reference serve distinct purposes: guides walk users through tasks, while reference records stable, exact behavior — and both are needed even when OpenAPI-generated docs exist. Choosing a safe, simple list endpoint as the first example helps verify authentication, base URL, and response handling without risking production data.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Beyond Authentication: Why API Authorization Failures Drive Most Security Breaches

Most API security breaches stem not from failed authentication but from flawed authorization, where verified users can access data belonging to others simply by altering a URL parameter. The most prevalent flaw, known as broken object-level authorization, occurs when an endpoint fetches a record by ID without confirming that the requesting user actually owns it. Experts recommend enforcing ownership checks directly within database queries rather than relying on application-layer logic that can be overlooked in future code changes. Other common vulnerabilities include over-returning sensitive data in API responses, mass assignment attacks, and unrestricted resource consumption that can enable both denial-of-service and billing abuse. The OWASP API Security Top 10 remains the standard reference for teams looking to systematically address these risks across their APIs.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Feature Flags Multiply Test Complexity — Here Is How to Manage It

Feature flags help teams control deployments, but each flag doubles the number of code states that require testing, making exhaustive coverage impractical. Developers are advised to focus testing on flag combinations that share the same code paths, while ensuring every individual flag is verified in both its enabled and disabled states. Applications should also define and test a fallback behavior for when the flag service itself becomes unavailable, typically defaulting to the disabled state. Automating flag-state tests within CI pipelines — using mocks rather than live flag servers — is recommended to keep coverage consistent and avoid QA burnout. Documenting the expected behavior for each flag state serves as a shared specification that guides test writing, code review, and the eventual safe removal of flags.

0 comments Read more at DEV Community