https://altsql.com/tags/postgresql/ Recent content in PostgreSQL on AltSql.com Hugo en-us Sat, 31 Oct 2026 00:00:00 +0000 https://altsql.com/altsql-restore-catches-a-cut-upload-and-a-72-percent-rental-loss-in-five-nights-of-pagila-backups/ Sat, 31 Oct 2026 00:00:00 +0000 https://altsql.com/altsql-restore-catches-a-cut-upload-and-a-72-percent-rental-loss-in-five-nights-of-pagila-backups/ <p>Pagila is the public sample database of a made-up DVD rental chain, a PostgreSQL port of MySQL&rsquo;s Sakila. It has customers, films, stores, 51,805 rentals and 51,061 payments, and the payments sit in one partition per month. That makes 69 tables in all, which is close enough to a small shop&rsquo;s real database to be worth a test.</p> <p>We loaded it into a local PostgreSQL 16.15 server and backed it up five times with <code>pg_dump | gzip</code>, the way many teams do it every night. After each backup, the released <code>altsql-restore</code> 0.5.0 checked the file with the same job name and the same history. The five runs were made one after another on 31 October 2026, and each one stands for a night.</p> https://altsql.com/altsql-restore-fails-three-postgresql-dumps-that-psql-restored-with-exit-status-0/ Sat, 31 Oct 2026 00:00:00 +0000 https://altsql.com/altsql-restore-fails-three-postgresql-dumps-that-psql-restored-with-exit-status-0/ <p>Plenty of teams already test their backups with a one-line script. It loads last night&rsquo;s dump into a spare database with <code>psql</code>, and if the exit status is 0, the backup counts as good. The trouble is that <code>psql</code> reading a file keeps going after an error. It prints the error, moves on to the next statement, and exits with 0 at the end, however many statements failed.</p> <p>We took three PostgreSQL dumps with real faults and gave each one to that script and to <code>altsql-restore</code> 0.5.0. Then we did the same with a MariaDB dump. Everything ran on 31 October 2026 against local PostgreSQL 16.15 and MariaDB 10.11.14 servers.</p>