#postgres
I upgraded the #postgres instance that the pod uses to use WAL-G 2.0.0, which looks to be a fairly substantial upgrade. For me it initially meant upgrading the encryption key used for backups from 20 bytes to 25 bytes (which pretty much necessitated starting a new stream of backups); everything else seems to be about the same.
WAL-G allows point-in-time-recovery (PITR) of Postgres databases to be stored on S3-compatible storage (including the FOSS Minio S3 server). It's continuous, leveraging Postgres' built-in write-ahead log (WAL) to provide the source data for the backups. WAL-G then compresses and (optionally) encrypts the data before sending it to your S3 storage.
If you're running a #Diaspora pod, you owe it to yourself and to your users to maintain reliable offsite backups. Once WAL-G is configured you can pretty much forget about it, except for occasional testing to make sure the backups are recoverable.
Decided to spin up a local k3s cluster running on my (ARM64) laptop. Another interesting bit about the Docker environment is how easy it is to migrate configurations across platforms.
I'll add that spinning up a cluster in k3s is just running a single command per node; one for the master node and one for each of the server nodes. It's trivial to automate and completes in seconds.
Now I'm messing around with #ceph for managing high-availability #storage (filesystem and #s3) and #stolon for high-availability #postgres.
#postgresql focusing on the wrong things... to help corporations remove dissenters https://www.postgresql.org/about/news/german-translation-of-community-code-of-conduct-posted-2414/ #psql #postgres
"pg_back is a tool that can dump all your databases to files, with the configuration of the server and roles/tablespaces definitions." https://www.postgresql.org/about/news/pg_back-210-released-2413/ #postgresql #psql #postgres
PostgreSQL: German #PostgreSQL Conference 2022 & Call for Papers ⚓ https://www.postgresql.org/about/news/german-postgresql-conference-2022-call-for-papers-2399/ ䷉ #postgres #de #germany #db
#PostgreSQL : #pgDay Paris #2022 — Schedule published ⚓ https://www.postgresql.org/about/news/pgday-paris-2022-schedule-published-2395/ ䷉ #postgres #psql
● NEWS ● #Rlang #Databases ☞ How To Connect R Shiny to #Postgres Database – The Definite Guide https://www.r-bloggers.com/2022/01/how-to-connect-r-shiny-to-postgres-database-the-definite-guide/
"The pgagroal community is happy to announce version 1.4.0." https://www.postgresql.org/about/news/pgagroal-140-2390/ #pgagroal #psql #postgres #postgresql
Many #PostgreSQL -Related Releases: JDBC, pg_query_rewrite, Foreign Data Wrapper for SQLite • Tux Machines ⇨ http://www.tuxmachines.org/node/159830 #psql #postgres #TuxMachines
● NEWS ● #Geshan #Databases ☞ #Postgres with #Docker and Docker compose a step-by-step guide for beginners https://geshan.com.np/blog/2021/12/docker-postgres/
"We have just released #PGSpider v2.0.0." https://www.postgresql.org/about/news/high-performance-sql-cluster-engine-pgspider-200-released-2384/ #PostgreSQL #psql #postgres
"The #Postgres #HEYHI team is happy to announce the release of version 3.0 of Database Lab Engine (DLE), the most advanced open-source software ever released that empowers development, testing, and troubleshooting environments for fast-growing projects." https://www.postgresql.org/about/news/database-lab-engine-30-ui-persistent-clones-postgresql-14-more-2376/
#PostgreSQL Weekly News - December 19, 2021 https://www.postgresql.org/about/news/postgresql-weekly-news-december-19-2021-2375/ #postgres #psql
PostgreSQL: #pgAdmin 4 v6.3 Released ⚓ https://www.postgresql.org/about/news/pgadmin-4-v63-released-2373/ ䷉ #postgresql #psql #postgres
Very bad optics. #postgres outsourcing guides to #microsoft #proprietarySoftware ... please do not become so self-harming... https://www.postgresql.org/about/news/publication-of-the-transition-guide-to-postgresql-2348/ http://techrights.org/wiki/index.php/Delete_Github
After upgrading to #postgres 14 I got strange errors whenever I tried to back up to a new bucket on my #S3 server in the basement. I ended up making a few other tweaks to the database (including upgrading it to Postgres 14.1), and the errors went away. Once again I have encrypted streaming offsite backups of the database, never more than ten minutes old, with daily checkpoints.
In another day or two I’ll delete the bucket that holds the ~150GB of Postgres 13 backups.