14th September 2023: PostgreSQL 16 Released!

Community Conference Recognition

Last updated: September 21, 2023. View change history. View history before December 8, 2020.

The Community Conference Recognition programme is a voluntary scheme under which submitters of events to the PostgreSQL Website listings may self-assess their entry against the criteria below, and if they comply may market their event as a PostgreSQL Community event.

Events that do not meet the criteria will still be welcomed (where appropriate under the general listing policies) - for example, events organised by a single company which may still be valuable for people to attend, but are not necessarily what we would consider fully "open."

Use of the terms "MUST", "MUST NOT", "SHOULD" and "SHOULD NOT" in the criteria below should be interpreted per RFC2119.


  • The event MUST be primarily focused on PostgreSQL and targeted at existing and/or potential developers and users of PostgreSQL.
  • The event MUST adopt and follow an appropriate Code of Conduct to ensure a safe and enjoyable environment for anyone who wishes to attend.
  • The event website, advertisments, notices, and any other related material MUST fully comply with the PostgreSQL Trademark Policy or receive permission from the PostgreSQL Community Association.
  • The PostgreSQL Core Team reserves the right to recognise, not recognise, or rescind a previous recognition for any event without justification.
  • Information that is required to be publicly disclosed MUST be available on the website of the event, or, if it is not possible to publish to the event’s website, MUST be made available in the PostgreSQL Website events list.
  • Events are self-certified as complying with these criteria when listed on the PostgreSQL Website. If an event is self-certified by the organisers and later found not to comply with the criteria, the PostgreSQL Core Team reserves the right to rescind the recognition of the event as a community event and, where appropriate, take further action up to a permanent ban on future event listings from the organisers.
  • These criteria may be reviewed and potentially updated at any time.


  • The organizing committee (also referred to as a steering committee) MUST be fully disclosed on the event website OR the PostgreSQL Website event listing.
  • The organizing committee SHOULD NOT consist of more than 50% members from a single company or group of companies under the same ultimate ownership or management.
  • Any benefits granted to the companies that employ the organisers MUST be considered sponsorship benefits.
  • The organizing committee MUST either:
    • Establish a code of conduct committee. The code of conduct committee MUST include at least one person who is not on the organizing committee. The membership of the code of conduct committee MUST be published. OR
    • Adopt the PostgreSQL Code of Conduct and refer code of conduct complaints to the PostgreSQL Code of Conduct Committee.

Talk Selection

  • The talk selection committee MUST be fully disclosed on the event website.
  • The talk selection committee MUST NOT consist of 50% or more members from a single company or group of companies under the same ultimate ownership or management.
  • All members of the talk committee MUST have an equal vote.
  • The Call For Papers MUST be open for anyone to submit.
  • Solicited or sponsor presentations may bypass the normal talk selection process, but MUST be approved by a majority of the talk selection committee.
  • The full talk selection process and voting system MUST be fully disclosed to all members of the talk selection committee.
  • Details of the talk selection process and how results were obtained MUST be provided to the PostgreSQL Core Team on request.


  • The sponsorship terms and/or prospectus MUST be published on the event website for public review.
  • All sponsors of the same level or type MUST be treated equally; they MUST be offered the same benefits at the same cost as all others.
  • Changes to the benefits offered SHOULD NOT be made following publication, and MUST NOT be made following the first executed sponsor agreement.
  • There SHOULD NOT be an exclusive top sponsorship level.
  • Sponsor benefits for all levels or types SHOULD include a listing on the event website. Ordering of the sponsor listing MUST be in randomised or predictable order with text stating how they are ordered, grouped by level or type of sponsorship.
  • Sponsorship opportunities SHOULD be open to all, offered on a first-come, first-served basis. Limits on the number of any given level or type of sponsorship may be set.
  • Only recognised sponsors may exhibit at the event, or be listed on the event website or other materials.


  • The event organisers MUST provide copies of financial records to the PostgreSQL Core Team or their nominated representative for review if requested. Any financial statements shared with the Core Team will not be distributed by the Core Team to any 3rd parties without written permission from the event organisers or where required by court order or other forms of legal authority.
  • A statement on the event website MUST indicate where any profits from the event will go, which specifically MUST support PostgreSQL community activities, either through:
    1. a recognized PostgreSQL Nonprofit Organisation
    2. a detailed list of how the profits will support ongoing PostgreSQL Global Development Group development
    3. to the future growth and expansion of the event, OR
    4. a PostgreSQL-related activity that supports the community at-large that can be validated by the PostgreSQL Core Team