"I treat production behavior as the real specification: isolate variables, find root causes, fix structurally so the failure class cannot recur."

name:              João Victor Mendes
role:              L2/L3 Technical Support Engineer
company:           Pedroso Automação  # B2B fiscal compliance ERP SaaS
location:          União da Vitória, PR, Brazil

specialty:         [PostgreSQL, Incident Response, ETL, Windows Server Automation]
clients:           500+ corporate  # 1500+ end-users
sla_compliance:    "95%+"
tickets_per_week:  80+

featured_now:
  - "incident-response-runbook  # PostgreSQL incident response + NVC + post-mortems"
  - "pg-incident-recovery      # Windows-first PostgreSQL multi-cluster recovery tool"
  - "windows-postgres-deployment-installer  # operator-assisted Windows PostgreSQL deployment automation"
  - "pg-restore-tool           # Windows-first local PostgreSQL restore utility for rebuild scenarios"

open_to:           [Support Engineering, Database Engineering, SRE]
contact:           linkedin.com/in/mendes-victor

incident-response-runbook

A production-grade PostgreSQL incident response framework that combines:

• WAL disk exhaustion recovery (pg_wal zero bytes free)
• SCRAM/MD5 and pg_hba.conf authentication failures
• Connection pool exhaustion and lock contention diagnosis
• Worked post-mortems for both infra and application-layer incidents
• NVC-based client communication and war-room protocols

This is the clearest public artifact of how I approach production systems: diagnose from first principles, document the failure mode precisely, and encode the fix so the class of incident does not recur.

pg-incident-recovery

A Windows-first PostgreSQL recovery orchestrator for multi-cluster hosts. It automates the safe parts of post-reboot incident handling:

• discovery of stopped PostgreSQL services
• data-directory resolution from service definitions
• stale postmaster.pid cleanup
• pg_controldata-based missing WAL triage
• parallel startup with bounded retries
• crash-recovery monitoring and clean handoff back to Windows SCM
• persistent queue files so interrupted runs can resume cleanly

This is the executable complement to the runbook repo: the runbook explains how I reason about incidents; this tool shows how I automate one of the ugliest recovery paths without crossing into unsafe automation.

windows-postgres-deployment-installer

An operator-assisted Windows 10/11 deployment baseline for PostgreSQL environments where agility and standardization matter more than infrastructure abstraction.

• PostgreSQL ZIP bootstrap with initdb, service registration, and config templating
• role synchronization, database creation, restore orchestration, and SQL validation
• conservative-by-default network posture with configurable listen addresses and LAN CIDRs
• operator-focused fallbacks designed to reduce manual install time from hours to minutes while preserving human review at the end

This repo shows how I think about deployment automation in support-heavy environments: automate the repetitive and failure-prone steps, make reruns safer, and still leave the final evaluation in human hands.

pg-restore-tool

A Windows-first PostgreSQL restore utility for a narrow support scenario: rebuilding a local or operator-controlled database quickly after workstation failure, reinstall, or environment corruption.

• restore profiles that separate safer session-level acceleration from explicitly unsafe cluster-wide durability tradeoffs
• operator-led database drop/recreate flow for offline rebuild cases
• backup validation, connection checks, and lightweight post-restore verification
• pragmatic framing: not a cloud backup platform, not PITR orchestration, not a live in-place restore system

This repo shows another part of my support engineering approach: encode the ugly recovery path honestly, preserve operator control, and make the risky parts explicit instead of hiding them behind vague automation.