WAL and PITR: When a pg_dump Is Not Enough
Turn on WAL archiving, take a base backup, and restore to a chosen timestamp so a bad write does not cost you a full day of PostgreSQL data.
NetBay journal
40 practical Databases articles from Netbay Engineering — written for operators running Linux and Windows VPS in India.
40 articles in this topic
Turn on WAL archiving, take a base backup, and restore to a chosen timestamp so a bad write does not cost you a full day of PostgreSQL data.
Set utf8mb4 and a modern collation at create time so emoji, Hindi text, and joins do not become a painful migration project later on a live VPS.
Use Redis pub/sub for live fan-out on one host, and skip it when you need persistence, retries, or consumer groups that Streams already provide.
Ship SQLite WAL frames to S3-compatible object storage with Litestream so a single VPS file has an off-site replica you can restore on demand.
Dump one PostgreSQL database in custom format, store it off the data disk, and restore it with pg_restore into a clean target cluster safely.
SQLite B-tree indexes match left-most prefixes, so LIKE with a leading percent cannot seek; use suffix indexes, FTS, or a stored reverse column.
Enable the slow query log, read EXPLAIN without folklore, and fix the table scans that actually burn CPU on a busy production MariaDB VPS host.
Store web sessions in Redis with short keys, SETEX TTLs, and cookie hygiene so logins survive app restarts without turning Redis into a public session dump.
Read EXPLAIN ANALYZE until you can tell a Seq Scan from an Index Scan, then add btree indexes that match filters, joins, and ORDER BY clauses.
Use sqlite3 .schema, EXPLAIN QUERY PLAN, and ANALYZE on the live file to see what SQLite stores, how it will read it, and which indexes it trusts.
Turn on MariaDB binary logs, take a consistent dump, and practice point-in-time recovery so a bad write is not a full-day restore from last night.
Put Redis in front of Postgres or MySQL with cache-aside reads, write-time invalidation, and TTLs so the cache stays a speed layer, not a second database.