Open Discussion Sessions
All seats are open to anyone. Meeting size is subject only to room size.
Example: The future of pg_stat_statements
Call For Proposals
We are now accepting proposals for many kinds of content for PGConf.dev 2026.
Wondering what you should propose?
- Presentations are structured sessions where speakers share knowledge, experiences, or new ideas in a traditional one-to-many format.
- Community Discussions are interactive sessions where participants discuss systemic community and technical challenges and brainstorm solutions.
- Workshops are educational sessions focused on enrichment and growing future Postgres contributors.
- Propose a Panel to have experts weigh in on community topics.
- Other Ideas include Community Office Hours to a group run, submit your ideas for enriching and connecting the community.
Presentation Sessions
Submission Deadline: January 16, 2026
Presentations are structured sessions where community members share knowledge, experiences, or new ideas with the PostgreSQL community. They come in two main formats:
- 25-Minute Talks — Short overviews highlighting specific contributions, proof-of-concept work, demos, and investigations or concise summaries and insights
- 50-Minute Talks — Deeper explorations, narratives, or educational content with a clear story arc used to present research, lessons learned, or systemic analysis
Presentations are meant to:
- Showcase technical contributions and research.
- Share lessons learned, both from successes and failures.
- Highlight community initiatives and needs.
- Educate and inspire discussion by surfacing new perspectives or practical techniques.
Some of the high level categories:
- Failed PostgreSQL projects and what you learned from them
- Proof-of-concept features and performance improvements
- Academic database research
- Long-form surveys and analyses of PostgreSQL problems
- Architectural issues in PostgreSQL and how to fix them
- New perspectives on systemic community concerns
- Educational content and how-tos
- Missing features and user needs
Submission Notes —
- Accepted talks confer at most two complimentary registrations. 25-minute talks with multiple speakers are unlikely to be accepted.
- Please propose your presentation as either a 50-minute or 25-minute talk. Do not submit the same proposal to both tracks.
Community Discussion Sessions
Deadline Batch 1: January 16, 2026, Batch 2: April 14th, 2026
Community discussion sessions are interactive sessions where you can discuss issues related to Postgres and the community in a meeting format.
These sessions will be scheduled for Tuesday and are a replacement for last year's interactive Tuesday content, including the Developer Meeting, the Community Summit, and the Extension Ecosystem Summit.
Community Discussion Sessions may concern any topic related to the Postgres community and Postgres ecosystem. While these sessions build on last year’s content, don't feel limited to previous topics. We’re eager to see new ideas that expand the conversation.
Their format should fall under one of the three following categories:
Working Groups
A small number of seats are reserved for invited members of the working group. The remaining slots are open to all conference attendees but seating will be organized to maximize collaboration amongst invited attendees. Please list invited participants in the body of your submission.
Example: Can the community support additional batch executors?
Closed Sessions
These sessions are for invited participants only and meant to create a focused, productive, and private discussion among those already involved in the topic. Please list invited participants in the body of your submission.
Example: Security committee discussing the impact of recent CVE
Submission Notes —
- Community discussion sessions do not confer complimentary registration.
- All invited attendees must be listed in the body of your proposal. Please secure invitees' consent prior to submitting your proposal. Organizers will do their best to avoid conflicts between meetings with overlapping key attendees.
- There are two CFP rounds for Community Discussion Sessions. Round one closes January 16, with most sessions chosen then. Round two closes April 14 to allow for late-breaking issues. Proposals not accepted in round one automatically roll over, so early submission improves your chances.
- No Community Discussion Sessions will be recorded.
Workshops
Submission Deadline: January 16, 2026
Have an idea for how to educate current and future Postgres hackers and extension developers? Submit a proposal for a hands-on practical training or collaborative workshop.
Example: Advanced Patch Feedback Session
Submission Notes
Accepted workshops confer at most two complimentary registrations.
Panels
Submission Deadline: January 16, 2026
Want to bring together experts to weigh in on an important community topic? From getting developers' perspectives on how to push a part of the project forward to sharing learnings about community organizing, panels are a great way to learn from the experienced members of the community and grow new leaders.
Example: Extension upgrades framework proposal evaluations
Submission Notes
- Accepted panels do not confer complimentary registration.
- Please list proposed panel members in the proposal. The list does not have to be finalized at submission, however you should ensure that all proposed members are open to participation.
Other Ideas?
Submission Deadline: January 16, 2026
From Community Office Hours to a group run, submit your ideas for enriching and connecting the community.
Don’t feel limited to previous formats or subjects — we’re eager to see new ideas that expand the conversation and enhance the experience.
Submission Rules and Tips
- Disclose if any portion of your session concerns closed source code.
- Proposed talks about your company's product are unlikely to be accepted unless they focus on how PostgreSQL could be modified to make it easier to extend and support.
- Describe in your bio what makes you uniquely positioned to deliver the content you are proposing.
- Community Discussion Sessions and Panels should feature individuals from multiple companies.
- Check out the PGConf.dev 2025 schedule to see what we accepted and for more inspiration.