Once upon a time, in a faraway server room encased in heavy glass and reinforced concrete, lived a PostgreSQL database so confined, so secluded, it could only dream of the cloud.

No network.

No USB.

No writable external storage device.

Just a keyboard, a monitor, and the hum of industrial-grade air filters.

This wasn’t your average air-gapped setup. This was a zero-exfiltration zone, with operational security so tight you’d think it was guarding state secrets—or worse, legacy banking software.

And yet, in this digital oubliette, one innocent challenge remained:
How do you back up a PostgreSQL database without ever extracting a file?

🎥 When Screens Are Your Network

Our customer didn’t just want backups—they needed them. The fear wasn’t theft, it was total failure: a motherboard dying quietly in its glass sarcophagus, taking the data with it. And if it came to that, chiseling through reinforced architecture wasn’t a viable disaster recovery plan.

We brainstormed everything:

• OCR of scrolling SQL dumps? Too lossy.
• Filming the psql output? Way too verbose.
• Printing out hex? Please, we’re not monsters.

And then came the epiphany: QR codes.

What if we could pg_dump the database…

into QR codes…

on the screen…

captured by a high-speed camera…

then reassembled frame by frame outside the vault?

It was so absurd, it just might work.

🧠 Hacking pg_dump: Now with More Pixels

PostgreSQL’s beloved pg_dump tool is modular. So we extended it with a custom archiver: --format=qrcode.

Here’s how it works:

1. QR encoding: Each chunk of SQL output is encoded into a PNG QR code.

2. Streaming: Instead of saving to disk, we push the stream of PNGs directly to stdout.

3. Framing: Our UI lays out multiple QR codes on a single screen using high-DPI output. (We’re talking 2000+ pixels here—room for a whole grid of codes.)

4. Playback: A dedicated machine with a 1280Hz high-speed camera films the screen, capturing the sequence as a video.

No keyboard macros. No sneaky uploads. Just photons and frames.

🔍 Reassembly Outside the Glass

Once the video is extracted from the glass box:

• Our parser watches the footage, frame by frame.

• QR codes are detected and decoded in parallel.

• Each chunk is sequence-tagged for ordering.

• The resulting text is reassembled into a proper pg_dump.sql.

And just like that: the database lives again—fully exported with no digital transfer.
Only light and lenses.

🧩 Notes on Performance & Fidelity

• QR Version: We used Version 40 QR codes (max capacity) with optimized binary mode for high density.

• Error Correction: Level Q for resilience under compression/artifacts.

• Screen Real Estate: 25×16 grid of codes per frame on a 1920×1080 pixel monitor—350 chunks per screen, around 1,016KB per frame.

• Playback Rate: We achieved ~60 screens/sec = 21,000 chunks/sec, nearly 60MB/sec!.

• Total Export Time: A full logical backup under 6GB was exported in less than 100 minutes!

🛡️ Why This Matters

This isn’t just a quirky story—it’s a reminder that PostgreSQL’s flexibility extends even into the absurd. Air-gapped systems aren’t rare in defense, finance, or critical infrastructure. And when normal tooling fails, PostgreSQL’s pluggable architecture gives you room to innovate, even in the tightest constraints.

We at Data Bene live for this kind of challenge. Whether it’s optimizing query plans or designing data exfiltration methods that look like spycraft, we’re here to help you make PostgreSQL dance—even when it’s stuck in a cage.

Want to try it yourself? Drop us a line—we love weird backups.

And if you’re thinking of streaming pg_restore into a laser light show, call us. We’re intrigued.