Call for Speakers

PG DATA 2026

Call for Speakers is closed. Submissions are no longer possible. Sorry.
in 4 months

PG DATA 2026

event starts

4 Jun 2026

event ends

5 Jun 2026

location

Chicago, Illinois, United States


PG DATA 2026 is the first event of a new conference series with an emphasis on education, developer community-building, and outreach to academia. 

The goals of PG DATA are:

To connect attendees with each other and with sponsors, and build our Midwestern and global Postgres community.

To draw diverse audiences of people in the technology field to learn about PostgreSQL: developers, DBAs, system administrators, technology leaders, consultants, students and academics, corporate professionals, and entrepreneurs.

To provide a unique forum to discuss the ongoing development and uses of PostgreSQL, and to help match user and commercial needs to roadmaps for development in the Postgres project and broader ecosystem.
finished 18 days ago
Call for Speakers
Call opens at 12:00 AM

06 Jan 2026

Call closes at 11:59 PM

07 Jan 2026

Call closes in Central Standard Time (UTC-06:00) timezone.
Closing time in your timezone () is .

Welcome to the PG DATA 2026 Call for Presentations!

We're looking for talks exploring PostgreSQL, using PostgreSQL, building on PostgreSQL, building for PostgreSQL, making community around PostgreSQL, anything else PostgreSQL. You might find inspiration in:

  • solving thorny data modeling problems with Postgres affordances
  • looking at application development with Postgres in hindsight
  • putting Postgres in the context of a wider data pipeline or system to discuss operations, deployment, or data movement
  • building software to manage Postgres, understand or interact with it more effectively, or extend its capabilities
  • thinking about how getting involved with Postgres affects community and career
  • exploring how internal Postgres subsystems work
  • deploying complex system architectures involving replication and failover, clustering, foreign data, and more
  • troubleshooting Postgres performance, stability, resilience, and other operational concerns
  • digging into the factors that made a Postgres deployment successful, or unsuccessful
  • administering "out of the ordinary" Postgres installations
  • discussing current or future Postgres development projects

This isn't an exhaustive list, of course. If it has a Postgres connection and fits inside 45 minutes, we want to hear about it!