Point-in-Time-Recovery on FromDual GmbH

MySQL table Point-in-Time-Recovery from mysqldump backup

oli.sennhauser@fromdual.com (Oli Sennhauser) — Sun, 25 Jan 2015 19:42:21 +0000

Sometimes we face the situation where we have a full MySQL database backup done with mysqldump and then we have to restore and recover just one single table out of our huge mysqldump file.
Further our mysqldump backup was taken hours ago so we want to recover all the changes on that table since our backup was taken up to the end.

Artificially Delayed Replication with PostgreSQL

oli.sennhauser@fromdual.com (Oli Sennhauser) — Mon, 03 Aug 2026 09:53:00 +0200

While working on our project titled “PostgreSQL for Dolphins and Sea Lions,” I pored over the PostgreSQL documentation on replication. What struck me was that PostgreSQL does NOT support artificially delayed replication—at least according to this documentation.

Backups Using the MySQL Clone Operation

oli.sennhauser@fromdual.com (Oli Sennhauser) — Tue, 28 Jul 2026 11:40:00 +0200

We recently tested the PostgreSQL backup tool pg_basebackup and were very impressed with its remote backup functionality, which allows for both physical local and physical remote backups.

PostgreSQL Point-in-Time Recovery with Oops-Queries

oli.sennhauser@fromdual.com (Oli Sennhauser) — Wed, 22 Jul 2026 17:26:00 +0200

While working on the topic “PostgreSQL for Dolphins and Sea Lions,” I discovered that in the PostgreSQL universe, the topic of point-in-time recovery tends to be sidestepped when it comes to specific statements or transactions. And when examples are provided, they primarily focus on DDL statements rather than DML statements.

Oops! - That SQL Query was not intended... Flashback

oli.sennhauser@fromdual.com (Oli Sennhauser) — Mon, 24 Jun 2019 14:12:00 +0200

It is Saturday night at 23:19. Time to go to bed after a hard migration day. Just a last clean-up query before finishing: Tap tap tap. Enter! - Oops!