PGSQL Phriday #014 is hosted by Pavlo Golub and we're talking about PostgreSQL events!

For this month’s #PGSQLPhriday 014 blogging event, Pavlo Golub has asked a pretty simple question: What do you think about PostgreSQL events? Prior to this year, I’d never attended an event focused on PostgreSQL. Heck, I’d never attended an event that had an intentional track or learning pathway, or whatever, focused on PostgreSQL. In the […] The post PostgreSQL Events – A Newbies Perspective: #PGSQLPhriday 014 appeared first on Grant Fritchey.

The PostgreSQL partition manager pg_partman is an open source extension widely supported and actively maintained by the PostgreSQL community.  pg_partman is an extension that streamlines the creation and management of table partition sets, supporting both time-based and serial-based partitioning approaches. You can use pg_partman to automate and create partitions by breaking large tables into smaller […]

This guide will delve into the seamless integration of PostgreSQL and Python, covering optimal connection methods and demonstrating how to execute CRUD operations (Create, Read, Update, Delete) efficiently within PostgreSQL using Python. The post PostgreSQL with Python – A Developer’s Guide appeared first on Stormatics.

Learn how to set up Postgres using Docker: this tutorial will help you install a PostgreSQL database using a Docker container. The post How To Set Up and Run a PostgreSQL Database Using Docker appeared first on Stormatics.

As PostgreSQL enthusiasts, we all know that the community’s heartbeat lies in PostgreSQL Events, whether local meetups, big conferences, or virtual gatherings, that have become prevalent during the COVID-19 pandemic. During a thrilling conference season, the PostgreSQL community is abuzz with activity. We’ve just wrapped up the PASS Data Community Summit, which featured a dedicated PostgreSQL presence that left us inspired and eager for more. The DOAG conference is underway, where numerous PostgreSQL experts are sharing their insights. And on the horizon, we eagerly anticipate the upcoming PostgreSQL Conference Europe in just a couple of weeks. I invite you to share your PostgreSQL Events experiences in your dedicated blog post. Whether you’re a seasoned attendee, a speaker, a trainer, a sponsor, an organizer, or a first-timer, your unique perspective contributes to the canvas of the PostgreSQL community. Reflecting on Personal Experiences and Favorite Moments Share the stories that resonate with you — the moments that left a lasting impression. Do you remember your first in-person event? Were there unexpected highlights or connections that made the event memorable for you? Unpacking PostgreSQL Events Highlights PostgreSQL events offer rich content, from training sessions to lightning talks. What were the standout sessions for you? Which speakers left you inspired or equipped with newfound wisdom? Share the gems you discovered during these sessions. Comparing Virtual and In-Person Experiences As the landscape of events evolves, so does the format. Reflect on your experiences attending both virtual and in-person events. What unique advantages and challenges does each setting present? How has the shift to virtual impacted your engagement with the PostgreSQL community? Networking and Collaborations For many of us, PostgreSQL events are more than just learning opportunities — they are epicenters for networking and collaboration. Discuss the importance of networking. Hav[...]

An introduction to database generated columns, using PostgreSQL and the new GeneratedField added in Django 5.0.

Authentication is the process of verifying the identity of a user or system attempting to access a database. In the realm of PostgreSQL, authentication serves as the first line of defense, ensuring that only authorized individuals or applications gain entry. As the gateway to sensitive data, robust authentication is imperative, safeguarding against unauthorized access and […] The post Unlocking Secure Connections: A Guide to PostgreSQL Authentication Methods appeared first on Stormatics.

We will guide you through the steps to connect to PostgreSQL in Delphi using Devart PgDAC. The post How to Connect to PostgreSQL in Delphi with Devart PgDAC appeared first on Devart Blog.

In recent blog post, I outlined a problem I hit with pg_dump. Specifically, pg_dump was picking up and using ~/.pgpass with pg_dump from PostgreSQL 12-14, but with PostgreSQL 15-16, it was failing. In this blog post: FreeBSD 13.2 PostgreSQL server 12 / 16 PostgreSQL client 12-16 Bacula 9.6.7 Today we figured out why: $HOME. $HOME for the script was set to / In PostgreSQL < 15, the code used the database to determine HOME and then pick up ~/.pgpass Stumbling through the environment variables In PostgreSQL 16, the code first checks $HOME (as shown in this commit). The order is now: PGPASSFILE $HOME/.pgpass (starting with v15) ~/.pgpass (i.e. the home directory from /etc/passwd) I stumbled across the problem this morning when pg_dump wasn’t running with a 16 client against a 16 server. The output was: 22-Nov 13:36 bacula-dir JobId 361250: Start Backup JobId 361250, Job=BackupCatalog.2023-11-22_13.36.38_39 22-Nov 13:36 bacula-dir JobId 361250: There are no more Jobs associated with Volume "FullAutoNoNextPool-04-17758". Marking it purged. 22-Nov 13:36 bacula-dir JobId 361250: All records pruned from Volume "FullAutoNoNextPool-04-17758"; marking it "Purged" 22-Nov 13:36 bacula-dir JobId 361250: Recycled volume "FullAutoNoNextPool-04-17758" 22-Nov 13:36 bacula-dir JobId 361250: Using Device "vDrive-FullFileNoNextPool-0" to write. 22-Nov 13:36 dbclone-fd JobId 361250: shell command: run ClientRunBeforeJob "/usr/local/bacula/dump_catalog.sh" 22-Nov 13:36 dbclone-fd JobId 361250: ClientRunBeforeJob: Password: 22-Nov 13:36 dbclone-fd JobId 361250: ClientRunBeforeJob: pg_dump: error: connection to server at "pg03.int.unixathome.org" (10.55.0.34), port 5432 failed: fe_sendauth: no password supplied 22-Nov 13:36 bacula-sd-04 JobId 361250: Recycled volume "FullAutoNoNextPool-04-17758" on File device "vDrive-FullFileNoNextPool-0" (/usr/local/bacula/volumes/FullFileNoNextPool), all previous data lost. 22-Nov 13:36 bacula-dir JobId 3612[...]