Call for Proposals · PGConf.dev 2027
Submit content to PGConf.dev 2027.
If you do something that makes PostgreSQL great, or would like to start, we want your ideas. Share your work, teach a skill, or bring people together.
- Presentations
- Share knowledge, experience, research, or a new idea in a structured 25 or 50-minute talk.
- Community discussions
- Work through systemic community and technical challenges together.
- Workshops
- Teach a practical skill or lead a collaborative working session.
- Panels
- Bring experienced voices together around an important community topic.
- Posters
- Present work visually and find co-authors, reviewers, or collaborators.
- Other ideas
- Propose office hours, a group activity, or a format we have not tried.
Important dates
- Main CFP closes
- 11:59 PM Montréal time
- CFP responses sent
- Discussion round 2 closes
- Round 2 responses sent
Why submit
Show us what you’re working on.
The program comes from work happening across PostgreSQL: patches and extensions, production lessons, research, education, community organizing, and ideas still taking shape.
You do not need a finished success story. Share what you learned, ask for feedback, teach something useful, or gather the people needed to move an idea forward.
Timeline
How the timeline works
The main CFP covers presentations, workshops, panels, and other ideas. The program committee reviews those proposals together and sends responses after the main round closes.
Community discussions can also be submitted in a second round for late-breaking topics. Proposals not selected in the first round roll over automatically.
Posters follow their own interest and final-PDF deadlines, listed with the poster details below.
Content type
Presentations
Submit a presentation
Presentations are structured sessions where community members share knowledge, experiences, or new ideas with the PostgreSQL community.
Propose a presentation as either a 25- or 50-minute talk. Do not submit the same proposal to both tracks.
- 25-minute talk
- A short overview of a contribution, proof of concept, investigation, or concise set of insights.
- 50-minute talk
- A deeper exploration, narrative, or educational session with a clear story arc for research, lessons learned, or systemic analysis.
Presentations are meant to:
- Showcase technical contributions and research.
- Share lessons learned from successes and failures.
- Highlight community initiatives and needs.
- Surface new perspectives or practical techniques.
This could be a failed project, a proof-of-concept feature, performance work, database research, an architectural problem, a community concern, a how-to, a missing feature, or an unmet user need.
Content type
Community discussions
Lead a community discussion
Community Discussion Sessions are interactive meetings where you can work through issues related to Postgres, its ecosystem, and its community.
Do not feel limited to subjects from previous years. We want new ideas that expand the conversation.
Community discussions have two types: open and closed. Choose the type that best fits your session when submitting your proposal. Neither type is recorded.
- Open
A small number of seats are reserved for key, invited participants.
The rest are open, with seating arranged to maximize collaboration among the invited attendees.
- Example: Multithreading Working Group
- Closed
- An invite-only, focused, productive, and private discussion among people already involved in the topic.
- Example: PostgreSQL Security Team Meeting
Please list every invited participant in the proposal and secure their consent before submitting. Organizers will try to avoid conflicts between sessions with overlapping key attendees.
Proposals not accepted in the first round roll over to the second automatically, so submitting early improves your chances.
Content type
Workshops
Teach a workshop
Have an idea for educating current and future Postgres hackers and extension developers? Propose a hands-on practical training or collaborative workshop.
For a past example, see How to read and write the SQL standard from 2026.
Accepted workshops confer at most two complimentary registrations.
Content type
Panels
Convene a panel
Bring together experts to weigh in on an important community topic, from deciding how to move part of the project forward to sharing lessons about community organizing and growing new leaders.
List proposed panelists. The list need not be final, but confirm that everyone named is open to participating.
For a past example, see Beyond the Source: The Human Architecture of PostgreSQL from 2026.
Panels do not confer complimentary registration.
Content type
Posters
Share a poster
Present your work visually and use it to attract co-authors, reviewers, and collaborators, or simply to improve discussion around a patch, extension, tool, or community initiative.
Boards are A1 size (594 × 841 mm), and capacity is limited to 20–30 posters. Posters are displayed during dedicated coffee and poster-session breaks. On-site presenters receive priority locations, but remote authors are welcome: we can print and display a poster and, in some cases, mail it back.
Core patches, bug fixes, extensions, tools, research, and community initiatives such as CI, testing, and diversity are all in scope. Commercial products are acceptable when they offer substantive technical content. Disclose closed-source work. Submissions that read as advertisements are unlikely to be accepted.
For past examples, see the 2026 posters.
Your poster should include
- A visual representation of the patch or project.
- The PGConf.dev 2027 conference logo.
- What attention or collaboration the project needs.
- Contact details, such as a QR code to the project or an email address.
When expressing interest, include your name, topic, and whether you expect to attend in person.
Accepted posters do not confer complimentary registration.
Content type
Other ideas
Pitch another idea
From Community Office Hours to a group run, propose an idea that enriches the conference and connects its community.
Do not feel limited to previous formats or subjects. We want ideas that expand the conversation and improve the experience.
Our new topic request forum lets you request a talk, support an idea, or gauge interest in one you might submit, so speakers and the program committee can see what people want.
Rules & tips
Increase your chances of acceptance.
- Disclose any part of a session that concerns closed-source code.
- Talks about a company's product are unlikely to be accepted unless they focus on how PostgreSQL could change to make the product easier to extend and support.
- Explain in your bio what uniquely positions you to deliver the proposed content.
- Community Discussion Sessions and panels should include people from multiple companies.
- Browse the PGConf.dev 2026 schedule to see what was accepted last year and find more inspiration.
Questions about the CFP?
Talk to the program team.
Email program@pgconf.dev with questions about formats, fit, or the submission process.