Call for Papers

Deadline: 2025-06-15

Talks may be on any topic related to PostgreSQL. Suggested topic areas include:

    • Developing applications with or for PostgreSQL
    • Administering large scale PostgreSQL installations
    • Case studies and/or success stories of PostgreSQL deployments (or interesting failures)
    • Tools and utilities
    • PostgreSQL internals hacking
    • Community and local user groups
    • Tuning and performance improvements
    • Migration from other database systems
    • Replication, clustering and high availability
    • Recovery and backup strategies
    • Benchmarking and hardware
    • PostgreSQL related products
    • DevOps and continuous deployment/configuration/integration around PostgreSQL
    • PostgreSQL and environmental problems
    • PostgreSQL and sustainable development

…of course, we’re happy to receive proposals for talks on other PostgreSQL related topics as well.

Submit your talk

Please tell us more about the topic you would like to speak about at PGDay Austria.

    Meet the Call for Papers Committee

    • Rafia Sabih – CYBERTEC

      Rafia Sabih – CYBERTEC

    • Oleksii Vasiliev - Railsware

      Oleksii Vasiliev – Railsware

    • Ryan Booz – Redgate

      Ryan Booz – Redgate

    • Pavlo Golub – CYBERTEC (non-voting member)

      Pavlo Golub – CYBERTEC (non-voting member)

    Selection Process

    We are often asked about the selection criteria and process for selecting the presentations among all the submitted proposals that will make up the schedule.

    All submissions are looked at and considered by the program committee by reading abstracts, titles, and submission notes. The program committee members each vote on every submission with a score of 1 through 9. It is customary to abstain from voting on submissions by coworkers. When a presenter has multiple submissions, the committee considers which subject will be the best fit for the conference as we try very hard to not have repeat speakers during the event. Submissions are also de-duplicated to minimise repetition, such that the schedule is balanced overall.

    Program committee members are an unpaid volunteer position. There are many talk submissions at every PostgreSQL Europe event so committee members often spend many hours reviewing submissions.

    The talks are then sorted by their average score and the final selection is made by the committee in conference calls amongst the top rated.

    Things to consider

    Abstract: To get a quick overview of a topic, an abstract is very important to us. It has shown over the years that a clear and concise abstract is a good indicator of a clear, understandable thought process and well received presentation. 

    The abstract should…

    • … be clear and to the point
    • …show the knowledge that will be gained by the audience
    • …be concise, do not post a full script!

    Submission Notes: Do not keep secrets or surprises from the committee. If your abstract teases the audience about some research or a new project you are planning to reveal during the talk, make sure you tell the committee what that is in the submissions notes. Your secrets are safe with us, but we need to know what the content of our conference is.

    Subject Relevancy: How clear is the connection to PostgreSQL? Broader topics are of course welcome, if the connection to PostgreSQL is made clear. Known speakers are generally more trusted to connect to PostgreSQL on general topics, so if in doubt make sure to include in the abstract how it relates to PostgreSQL.

    Speaker Profile: Please make sure that you have filled out the speaker profile. The profile will be published for all scheduled talks later. Theses profiles should help the attendees to select your talk when planning their day at the event. 

    Number of Speakers: We prefer that a talk is delivered by one speaker, two at max. When submitting a talk, please add a speaker note with the name of the additional speaker. If your talk requires more than 2 speakers in total, please contact us.