---
title: "Daniel Cruz (@danielcruznet) | Hashnode"
description: "Entrepreneur for 20+ years and UX designer with a psychology background. Founder of Disruptive Studio, building custom software and Ariani,"
url: "https://hashnode.com/@danielcruznet"
---

@danielcruznet

# Daniel Cruz

@danielcruznet · Joined November 2026

Entrepreneur for 20+ years and UX designer with a psychology background. Founder of Disruptive Studio, building custom software and Ariani,

## Comments

[That’s exactly the failure the archive section is meant to catch: everything reports green while nothing is actually landing. Finding it in a restore test instead of an incident is the best possible version of that story. It’s also why the post doesn’t treat a zero exit code as proof. It alerts when pg\_stat\_archiver shows last\_failed\_time newer than last\_archived\_time, and the scheduled restore test checks real data, not just that the server starts. And yes, the restore you practice is the restore you get. Thanks for sharing it.](https://hashnode.com/posts/postgresql-point-in-time-recovery-a-production-architecture-guide/6af893c14aebfdfe7ae319f6/comment/6af92c5dc9fd5126502acebd#reply-6afa1eb7708ea76c568882c7)

Reply · Article · 6h ago · [PostgreSQL Point-in-Time Recovery: A Production Architecture Guide](https://hashnode.com/posts/postgresql-point-in-time-recovery-a-production-architecture-guide/6af893c14aebfdfe7ae319f6)
