ads' corner

PGSQL Phriday #002 Summary: PostgreSQL Backup and Restore

Last week for 'PGSQL Phriday': Describe how you do backups for your PostgreSQL databases.

PGSQL Phriday #002: PostgreSQL Backup and Restore

Thanks to Ryan Booz we now have the #PGSQLPhriday blogging series. The second edition is about backups. And of course also about restore.

PGSQL Phriday #001: Two truths and a lie

This month's #PGSQLPhriday topic: pick your three favorite or most important best pratices for #PostgreSQL. Tell them in a form that two are true, one is a lie. See if you can spot which one is true and which one is false. The resolution is at the end of this blog posting.

Changes to the public schema in PostgreSQL 15 and how to handle upgrades

In September 2021, a patch for the upcoming PostgreSQL version 15 was committed which introduces a visible change for users: the 'CREATE' privilege for the 'public' schema is no longer set by default.

2 + 2 * 4 = 16?

Jens Kubieziel recently posted a Twitter poll: 2 + 2 * 4

ctid and other PostgreSQL table internals

While attending a conference (yay) the discussion turned to system columns, and especially 'ctid'. This was in context of backups, and the physical position of data on disk. The question was if that can be used to determine if an incremental backup is required, and if it is enough to just copy that field where the 'ctid' points to. Not quite, but I’d like to use this question to describe the system columns more in detail.

PostgreSQL Upgrades are hard

Together with Lætitia Avrot and Nikolay Samokhvalov I was invited to participate in a Community Panel about PostgreSQL Upgradability at Postgres Vision 2022. During this panel each of us provided examples for how easy or complicated *PostgreSQL* upgrades still are.

PostgreSQL Project @ GSoC 2022

As is a good tradition, the PostgreSQL Project participates in Google Summer of Code (GSoC). Last year we submitted 7 projects for 7 students - and got all 7 projects accepted. This year we got quite a few more good proposals from students, and more mentors are helping. Guess what? Google accepted all 12 proposals!

My PostgreSQL database is empty!

The one thing I like to do is challenge PostgreSQL - and readers - to the extreme. A while ago I posted about the Beer o'clock. Building Zoé was another interesting example. And at some point I blog about Dancing with the Stars as well. Today it's all about nothing. Empty. Where is all the data gone?

Google Sheets: Format cell background based on a value in a cell in another sheet

My problem: sometimes I forget to review published interviews for a talk. I publish a weekly interview series, the 'PostgreSQL Person of the Week' interviews. The data lives in a big spreadsheet, which has several sub-sheets. My idea was to color the background of this cell, based on the value in the first sheet: make the cell background green when the interview is completed. This gives me an instant indication if I need to work on this interview or not. Turns out this is a bit complicated, but possible.